Skip to main content
VulnerabilityPublished

CVE-2026-52855: pterodactyl wings · Information Exposure

Affects pterodactyl wingsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 1.12.3 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.12.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade wings and pterodactyl/wings to 1.12.3.

Affected software

ProductAffectedFixed in
pterodactylwingsAffected
  • <1.12.3
Fixed in
  • 1.12.3
GitHubpterodactyl/wingspkg:github/pterodactyl/wingsOther threatsAffected
  • <1.12.3
Fixed in
  • 1.12.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Pterodactyl Wings to version 1.12.3 or later, where this vulnerability is fixed. No other mitigation guidance is provided or required as the fix is official and available.

Description

Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.12.3, {{config.}} placeholders in egg configuration-file templates allow a low-privileged user to read {{config.token}}, {{config.token_id}}, and {{config.docker.registries}} from the full daemon configuration. This issue is fixed in version 1.12.3.

References

Community reviews

Loading reviews…