Wings exposes node configuration secrets through egg configuration-file templating
CVE-2026-52855GHSA-pfvc-3p5h-x7h6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/pterodactyl/wings 1.12.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/pterodactyl/wings
- Affected
- < 1.12.3
- Fixed in
- 1.12.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pfvc-3p5h-x7h6 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6158 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pfvc-3p5h-x7h6 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- EPSS
- CVE-2026-52855: 0.51% estimated exploitation activity in the next 30 days; percentile 43.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Type: Exposure of sensitive information / insufficiently protected credentials leading to privilege escalation and full node compromise. Wings exposes its entire daemon configuration to the egg configuration-file templating engine. When Wings renders a server's configuration files, any {{config.<path}} placeholder in a replacement value is resolved against the full marshalled daemon configuration, with no restriction on which paths may be read. Because the Panel substitutes user-controlled egg variable values into these replacements before sending them to Wings, a low-privileged user can smuggle a {{config.}} placeholder through a variable value. The placeholder is then resolved by Wings and written into a file inside the user's own server, where it can be read via the file manager or SFTP. This allows reading, among other values: - {{config.token}} - the node's daemon token, which is both the API bearer for the Panel⇆Wings channel and the HMAC signing key for every JWT the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-pfvc-3p5h-x7h6
- Revision 2 · amended ·
Amended from osv record GO-2026-6158
- Revision 1 · created ·
Published from osv record GHSA-pfvc-3p5h-x7h6
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-52855 Advisory: Wings exposes node configuration secrets through egg configuration-file templating IDs: CVE-2026-52855, GHSA-pfvc-3p5h-x7h6 Record: https://patchnext.com/advisories/cve-2026-52855 (revision 3, source checked 26 Oct 2026, 15:27 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/pterodactyl/wings 1.12.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/pterodactyl/wings: affected < 1.12.3; fixed in 1.12.3 ## Suggested inspection (read-only) - Go github.com/pterodactyl/wings: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/pterodactyl/wings. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-pfvc-3p5h-x7h6 (OSV record GHSA-pfvc-3p5h-x7h6 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6158 (OSV record GO-2026-6158 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3 (fixed)) - Verified: https://github.com/advisories/GHSA-pfvc-3p5h-x7h6 (GitHub-reviewed advisory GHSA-pfvc-3p5h-x7h6 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.3) Commands are suggestions: review each one before running it.
Loading voting…