CVE-2026-54593
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPterodactyl is a free, open-source game server management panel. Prior to Panel version 1.12.3 and Wings version 1.12.2, the Wings /upload/file endpoint accepted any valid panel-signed JWT that contained server_uuid, user_uuid, and unique_id claims without checking the token's intended purpose; because the Panel issues JWTs carrying those same claims for lower-privilege operations such as WebSocket authentication and file-download links, an authenticated subuser could reuse one of those tokens (for example a WebSocket token obtained with only the websocket.connect permission) by replaying it against /upload/file to write arbitrary files to the same server, despite never being granted the file.create permission. This issue is fixed in Panel version 1.12.3 and Wings version 1.12.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authorization bypass vulnerability in Pterodactyl Wings where the /upload/file endpoint accepts any valid panel-signed JWT containing server_uuid, user_uuid, and unique_id claims without verifying the token's intended purpose. An authenticated subuser with only websocket.connect permission can obtain a JWT for a lower-privilege operation and replay it against the file upload endpoint to write arbitrary files, bypassing the file.create permission requirement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Wings versionRun 'wings --version' or check the wings binary version on the nodeAffected if Wings version is below 1.12.2
-
Check if file upload endpoint accepts JWTsReview Wings daemon configuration for JWT authentication settings on the /upload/file routeAffected if JWT validation is enabled without purpose/audience verification
-
Verify JWT token validation logicInspect the Wings API handler for /upload/file and check if token validation includes purpose or audience claims matching the endpointAffected if JWT validation accepts any valid panel-signed JWT without checking token purpose for the specific endpoint
-
Test subuser authorization boundaryAs a subuser with only websocket.connect permission, attempt to obtain a JWT and replay it against the /upload/file endpointAffected if The file upload endpoint accepts JWTs intended for websocket operations, bypassing file.create permission check
If Wings version is below 1.12.2 and the upload endpoint accepts JWTs without validating token purpose, the environment is affected by this authorization bypass.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Pterodactyl Panel to version 1.12.3 and Wings to version 1.12.2, which implement proper token purpose validation to ensure JWTs are only accepted by their intended endpoints.
Panel 1.12.3 / Wings 1.12.2
- Upgrade Pterodactyl Panel to version 1.12.3 or later
- Upgrade Pterodactyl Wings to version 1.12.2 or later
- After upgrading, verify that JWT tokens are now properly validated for their intended purpose
- Confirm that subusers without file.create permission can no longer upload files using WebSocket or file-download tokens
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54593 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data