CVE-2026-52855: Github.com/pterodactyl/wings Wings Exposes Node Configuration Secrets Vulnerability

CRITICAL
Advisory Identifier: GHSA-pfvc-3p5h-x7h6
CVSS 9.9
CWE-522 CWE-200
Published
Advisory Summary

CVE-2026-52855 is a CRITICAL (CVSS 9.9) wings exposes node configuration secrets vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Github.com/pterodactyl/wings libraries in the Go ecosystem. The issue involves wings exposes node configuration secrets through egg configuration-file templating. Remediation is available by upgrading affected packages to version 1.12.3.

CVE-2026-52855 at a Glance

CVE Identifier CVE-2026-52855
GHSA Identifier GHSA-pfvc-3p5h-x7h6
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Github.com/pterodactyl/wings
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-52855

To remediate this vulnerability, upgrade all affected Github.com/pterodactyl/wings dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/pterodactyl/wings fixed: 1.12.3
Upgrade github.com/pterodactyl/wings to 1.12.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/pterodactyl/wings

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-52855, inspect your project dependencies for Github.com/pterodactyl/wings:

inspect dependencies for github.com/pterodactyl/wings

Analyze the terminal output to locate any version of Github.com/pterodactyl/wings in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.12.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Github.com/pterodactyl/wings, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 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 multi-tenant / shared-hosting deployments are affected. **Resulting impact:** Disclosure of the node daemon token lets the attacker forge authentication tokens and act against **every server on that node**, a full-node compromise reachable from a low-privileged account. ### Patches Yes. Fixed in **Wings `v1.12.3`** (Panel is unaffected; the fix is Wings-only). Wings no longer exposes its full configuration to the templating engine only an explicit, non-secret subset (the Docker network interface) can be resolved by `{{config.*}}` placeholders. Users should upgrade Wings to `v1.12.3` or later. **After upgrading, rotate the affected nodes' daemon tokens**, since a previously exfiltrated token remains valid until rotated (Admin → Nodes → Configuration → reset the token, then re-deploy `config.yml` to the node). ### Workarounds For operators who cannot upgrade immediately: - Audit your eggs and ensure no **user-editable** variable is rendered into a   configuration file, or mark such variables non-editable. These reduce exposure but are not a complete fix; upgrading Wings is the recommended action.

CVE-2026-52855 Affected Github.com/pterodactyl/wings Versions

1 component(s)
Fixed Versions:
1.12.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/pterodactyl/wings
Go
< 1.12.3
1.12.3

References

Frequently Asked Questions

What is CVE-2026-52855?
CVE-2026-52855 is a security vulnerability in Github.com/pterodactyl/wings involving Wings exposes node configuration secrets through egg configuration-file templating under CWE-522: Insufficiently Protected Credentials.
Which Github.com/pterodactyl/wings versions are affected?
Affected versions include releases prior to 1.12.3 across affected packages: github.com/pterodactyl/wings.
What version fixes CVE-2026-52855?
Upgrading to 1.12.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/pterodactyl/wings affected?
Yes, github.com/pterodactyl/wings is affected in releases prior to 1.12.3. Upgrade your dependency to 1.12.3 or later.
What is the CVSS score of CVE-2026-52855?
CVE-2026-52855 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-52855?
CVE-2026-52855 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check Go dependencies for CVE-2026-52855?
Run the dependency tree command: 'inspect dependencies for github.com/pterodactyl/wings'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pfvc-3p5h-x7h6",
  "modified" : "2026-07-31T16:16:46Z",
  "published" : "2026-07-31T16:16:46Z",
  "aliases" : [ "CVE-2026-52855" ],
  "summary" : "Wings exposes node configuration secrets through egg configuration-file templating",
  "details" : "### Impact\n\n**Type:** Exposure of sensitive information / insufficiently protected credentials\nleading to privilege escalation and full node compromise.\n\nWings exposes its **entire** daemon configuration to the egg configuration-file\ntemplating engine. When Wings renders a server's configuration files, any\n`{{config.<path>}}` placeholder in a replacement value is resolved against the\nfull marshalled daemon configuration, with no restriction on which paths may be\nread.\n\nBecause the Panel substitutes **user-controlled** egg variable values into these\nreplacements before sending them to Wings, a low-privileged user can smuggle a\n`{{config.*}}` placeholder through a variable value. The placeholder is then\nresolved by Wings and written into a file inside the user's own server, where it\ncan be read via the file manager or SFTP.\n\nThis allows reading, among other values:\n\n- `{{config.token}}` - the node's daemon token, which is both the API bearer for\n  the Panel⇆Wings channel **and** the HMAC signing key for every JWT the node\n  issues;\n- `{{config.token_id}}`;\n- `{{config.docker.registries}}` - configured container-registry credentials.\n\n**Who is impacted:** Any deployment where a user who is not fully trusted can set\nan egg variable value (e.g. a server owner or a subuser with the `startup.update`\npermission) **and** the server's egg renders a user-editable variable into a\nconfiguration file via `{{server.build.env.*}}`. This pattern is common across\nstock and community eggs, so most multi-tenant / shared-hosting deployments are\naffected.\n\n**Resulting impact:** Disclosure of the node daemon token lets the attacker forge\nauthentication tokens and act against **every server on that node**, a full-node compromise reachable from a low-privileged\naccount.\n\n### Patches\n\nYes. Fixed in **Wings `v1.12.3`** (Panel is unaffected; the fix is Wings-only).\n\nWings no longer exposes its full configuration to the templating engine only an\nexplicit, non-secret subset (the Docker network interface) can be resolved by\n`{{config.*}}` placeholders.\n\nUsers should upgrade Wings to `v1.12.3` or later.\n\n**After upgrading, rotate the affected nodes' daemon tokens**, since a previously\nexfiltrated token remains valid until rotated (Admin → Nodes → Configuration →\nreset the token, then re-deploy `config.yml` to the node).\n\n### Workarounds\n\nFor operators who cannot upgrade immediately:\n\n- Audit your eggs and ensure no **user-editable** variable is rendered into a\n  configuration file, or mark such variables non-editable.\n\nThese reduce exposure but are not a complete fix; upgrading Wings is the\nrecommended action.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/pterodactyl/wings"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.12.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pterodactyl/wings/security/advisories/GHSA-pfvc-3p5h-x7h6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pterodactyl/wings/commit/eb65e27ae077a63e38518c490768486af1cd86a9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pterodactyl/wings"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pterodactyl/wings/releases/tag/v1.12.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-522" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-31T16:16:46Z",
    "nvd_published_at" : null
  }
}