CVE-2026-52857: config parser DoS exhausts memory

CISO Take

Wings, the daemon that runs game servers under the Pterodactyl panel, ships JSON/YAML/XML configuration parsers in parser.go that impose no size limit, so a locally authorized user can submit an oversized non-file configuration entry and exhaust the Wings process's memory, crashing the daemon and every game server it manages. This is flagged in our feed under the ml_ui AI category, but Pterodactyl Wings is a game-server hosting control plane with no AI/ML functionality — that categorization appears to be a false positive from the ingestion pipeline and should be corrected rather than treated as an AI-stack risk. The bug itself is low severity in absolute terms (CVSS 5.5, local vector, low privileges, no public exploit, not in CISA KEV, no EPSS score published) and is purely an availability issue with no confidentiality or integrity impact. For organizations that do run Pterodactyl/Wings for game-server hosting, the fix is straightforward: upgrade to Wings 1.13.0 or later, where the parsers enforce bounds on configuration input size.

Sources: NVD GitHub Advisory

What is the risk?

Low overall risk. The attack vector is local, requires low privileges, and needs no user interaction, but exploitation only yields a denial-of-service (availability impact: High; confidentiality and integrity impact: None). There is no evidence of active exploitation, no CISA KEV listing, no published EPSS score, and no public exploit code or Nuclei template. This is not an AI/ML-relevant vulnerability — Wings is a game-server management daemon, unrelated to model serving, inference, or AI pipelines — so it carries no incremental risk to AI/ML operations.

How does the attack unfold?

Initial Access

A low-privileged, authenticated user with permission to manage a server instance gains access to submit a configuration file to Wings.

Exploitation

The user submits an oversized non-file JSON, YAML, or XML configuration payload that the unbounded parser attempts to load fully into memory.

Impact

Wings process memory is exhausted, crashing or hanging the daemon and causing a denial of service for all game servers it manages.

Initial Access

A low-privileged, authenticated user with permission to manage a server instance gains access to submit a configuration file to Wings.

Exploitation

The user submits an oversized non-file JSON, YAML, or XML configuration payload that the unbounded parser attempts to load fully into memory.

Impact

Wings process memory is exhausted, crashing or hanging the daemon and causing a denial of service for all game servers it manages.

How severe is it?

CVSS 3.1

5.5 / 10

EPSS

0.1%

chance of exploitation in 30 days

Higher than 2% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AV Local

AC Low

PR Low

UI None

S Unchanged

C None

I None

A High

What should I do?

1 step

Upgrade Wings to version 1.13.0 or later, which adds size bounds to the JSON/YAML/XML configuration parsers in parser.go. Until patched, restrict which users/tenants can submit or modify server configuration files, and monitor the Wings process for abnormal memory growth or OOM-kill events as a detection signal. Organizations that do not operate Pterodactyl/Wings have no action to take; this CVE should be re-tagged out of the ml_ui/AI category in the internal feed.

What does CISA's SSVC say?

Decision Track

Exploitation none

Automatable No

Technical Impact partial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

DoS

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-52857?

Wings, the daemon that runs game servers under the Pterodactyl panel, ships JSON/YAML/XML configuration parsers in parser.go that impose no size limit, so a locally authorized user can submit an oversized non-file configuration entry and exhaust the Wings process's memory, crashing the daemon and every game server it manages. This is flagged in our feed under the ml_ui AI category, but Pterodactyl Wings is a game-server hosting control plane with no AI/ML functionality — that categorization appears to be a false positive from the ingestion pipeline and should be corrected rather than treated as an AI-stack risk. The bug itself is low severity in absolute terms (CVSS 5.5, local vector, low privileges, no public exploit, not in CISA KEV, no EPSS score published) and is purely an availability issue with no confidentiality or integrity impact. For organizations that do run Pterodactyl/Wings for game-server hosting, the fix is straightforward: upgrade to Wings 1.13.0 or later, where the parsers enforce bounds on configuration input size.

Is CVE-2026-52857 actively exploited?

No confirmed active exploitation of CVE-2026-52857 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-52857?

Upgrade Wings to version 1.13.0 or later, which adds size bounds to the JSON/YAML/XML configuration parsers in parser.go. Until patched, restrict which users/tenants can submit or modify server configuration files, and monitor the Wings process for abnormal memory growth or OOM-kill events as a detection signal. Organizations that do not operate Pterodactyl/Wings have no action to take; this CVE should be re-tagged out of the ml_ui/AI category in the internal feed.

What is the CVSS score for CVE-2026-52857?

CVE-2026-52857 has a CVSS v3.1 base score of 5.5 (MEDIUM). The EPSS exploitation probability is 0.11%.

What are the technical details?

Original Advisory

Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.13.0, unbounded json, yaml, and xml configuration-file parsers in parser.go can process an oversized non-file parser configuration file and exhaust Wings process memory. This issue is fixed in version 1.13.0.

Exploitation Scenario

On a multi-tenant Pterodactyl hosting platform, a customer with low-privilege access to their own game server instance submits a crafted, extremely large JSON, YAML, or XML configuration payload through the panel-to-Wings interface. Because parser.go reads the entire input into memory without a size cap, the Wings daemon's memory usage spikes and the process is killed or becomes unresponsive, taking down all game servers it manages on that host — a tenant-triggered denial of service against shared infrastructure, with no code execution or data exposure involved.

Weaknesses (CWE)

CWE-400 Uncontrolled Resource Consumption CWE-400 Uncontrolled Resource Consumption

CWE-400 — Uncontrolled Resource Consumption: The product does not properly control the allocation and maintenance of a limited resource.

[Architecture and Design] Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
[Architecture and Design] Mitigation of resource exhaustion attacks requires that the target system either: The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker. recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.

Source: MITRE CWE corpus.