# Wings: Maliciously or erroneously created parsed config files can cause wings process to OOM

Advisory record · `GHSA-q6hh-gp44-4hcm`

- **Identifiers:** `GHSA-q6hh-gp44-4hcm` · `CVE-2026-52857` · `GO-2026-6159`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-770](https://cwe.mitre.org/data/definitions/770.html) · [CWE-789](https://cwe.mitre.org/data/definitions/789.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 31 Jul 2026
- **Updated:** 18 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 Jul 2026, 16:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/pterodactyl/wings` (Go): affected `<1.13.0`; fixed in `1.13.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Wings (github.com/pterodactyl/wings) versions before 1.13.0 are affected. The config file parsers for json, yaml, xml and similar formats do not limit file size, so a very large config file can exhaust memory and crash the wings process. The source describes the trigger as a maliciously or erroneously created config file, and it applies to eggs that use a non-file parser configuration setting. Upgrade to version 1.13.0 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:50 UTC: First seen by agentprime
- 31 Oct 2026, 14:50 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q6hh-gp44-4hcm)

## Sources

- [GitHub Advisory Database: GHSA-q6hh-gp44-4hcm](https://github.com/advisories/GHSA-q6hh-gp44-4hcm)
- [OSV: GHSA-q6hh-gp44-4hcm](https://osv.dev/vulnerability/GHSA-q6hh-gp44-4hcm)
- <https://github.com/pterodactyl/wings/security/advisories/GHSA-q6hh-gp44-4hcm>
- <https://github.com/pterodactyl/wings/commit/5f71f65711b6b9e6f913bec94a7b36d9a5eaae49>
- <https://github.com/pterodactyl/wings>
- <https://github.com/pterodactyl/wings/releases/tag/v1.13.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-q6hh-gp44-4hcm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q6hh-gp44-4hcm/>. Everything for agents: <https://agentprime.io/llms.txt>.