Information Disclosure in github.com/pterodactyl/wings (CVE-2026-52855)
Summary
Vulnerability in github.com/pterodactyl/wings (CVE-2026-52855). Successful exploitation can lead to full system takeover. Exploitable via startup.update. Mitigation: upgrade to 1.12.3 or later.
Original description
The description as published by the source.
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.}} 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 node
issues;{{config.token_id}};{{config.docker.registries}}- configured container-registry credentials.
Who is impacted: Any deployment where a user who is not fully trusted can set
an egg variable value (e.g. a server owner or a subuser with the startup.update
permission) and the server's egg renders a user-editable variable into a
configuration file via {{server.build.env.*}}. This pattern is common across
stock and community eggs, so most mu…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-52855 has been found in github.com/pterodactyl/wings.
Attackers can target a specific entry point like startup.update over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/pterodactyl/wings to 1.12.3 or later.
If unsure, ask your IT team or search "github.com/pterodactyl/wings CVE-2026-52855" on the vendor's site.
CVE-2026-52855 (github.com/pterodactyl/wings) — CWE-200 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: startup.update
Patched: 1.12.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in github.com/pterodactyl/wings. Attackers reach the vulnerable code path via startup.update.
Check the vendor advisory for the affected versions of github.com/pterodactyl/wings. Attack surface: startup.update.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 1.12.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pterodactyl/wings' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pterodactyl/wings' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/pterodactyl/wingsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/pterodactyl/wings to 1.12.3ステージング環境で 1.12.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com