CVE-2026-54593: Pterodactyl/panel Pterodactyl's Improper JWT Scoping Allows Vulnerability
HIGHCVE-2026-54593 is a HIGH (CVSS 8.1) pterodactyl's improper jwt scoping allows vulnerability (CWE-1259: Improper Restriction of Security Token Assignment) affecting Pterodactyl/panel libraries in the Packagist ecosystem. The issue involves pterodactyl's improper jwt scoping allows subuser to upload files when not explicitly granted `file.create` permissions. Remediation is available by upgrading affected packages to version 1.12.3, 1.12.2.
CVE-2026-54593 at a Glance
Security Impact
CVSS: 8.1
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:U/C:N/I:H/A:H).
How to Fix CVE-2026-54593
To remediate this vulnerability, upgrade all affected Pterodactyl/panel dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade pterodactyl/panel to 1.12.3
Upgrade github.com/pterodactyl/wings to 1.12.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for pterodactyl/panel
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-54593, inspect your project dependencies for Pterodactyl/panel:
inspect dependencies for pterodactyl/panel
Analyze the terminal output to locate any version of Pterodactyl/panel 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-1259: Improper Restriction of Security Token Assignment, where the system-on-a-chip (soc) implements a security token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. however, the security tokens are improperly protected. In Pterodactyl/panel, 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
CVE-2026-54593 Affected Pterodactyl/panel Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
pterodactyl/panel
|
Packagist |
< 1.12.3
|
1.12.3
|
|
github.com/pterodactyl/wings
|
Go |
< 1.12.2
|
1.12.2
|
References
Frequently Asked Questions
What is CVE-2026-54593?
Which Pterodactyl/panel versions are affected?
What version fixes CVE-2026-54593?
Is pterodactyl/panel affected?
Is github.com/pterodactyl/wings affected?
What is the CVSS score of CVE-2026-54593?
What CWE is associated with CVE-2026-54593?
How can I check Packagist dependencies for CVE-2026-54593?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8r6w-3qq5-4p4r",
"modified" : "2026-07-28T15:43:25Z",
"published" : "2026-07-28T15:43:25Z",
"aliases" : [ "CVE-2026-54593" ],
"summary" : "Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions",
"details" : "### Summary\nA privilege escalation vulnerability exists in the Wings /upload/file endpoint due to insufficient validation of panel-signed JWTs. Wings accepts any valid panel-signed JWT containing `server_uuid`, `user_uuid`, and `unique_id`, regardless of the token’s intended purpose. Because the Panel issues JWTs with these same claims for other lower-privilege operations (such as WebSocket authentication and file download links), an authenticated subuser can reuse one of those tokens to upload arbitrary files without possessing the required `file.create` permission.\n\n### Impact\nAny subuser with permission to connect to a server's console, download files, or download backups could reuse those tokens to upload arbitrary files to the _same server_. A user that does not have access to a server as a subuser is not able to arbitrarily upload files.\n\n### Details\nThe panel generated JWT tokens for various purposes:\n- https://github.com/pterodactyl/panel/blob/0f82c105201b192d229f6abd5827e2ee7e672a05/app/Services/Backups/DownloadLinkService.php#L33-L36\n- https://github.com/pterodactyl/panel/blob/0f82c105201b192d229f6abd5827e2ee7e672a05/app/Http/Controllers/Api/Client/Servers/FileUploadController.php#L45\n- https://github.com/pterodactyl/panel/blob/0f82c105201b192d229f6abd5827e2ee7e672a05/app/Http/Controllers/Api/Client/Servers/WebsocketController.php#L58-L61\n- https://github.com/pterodactyl/panel/blob/0f82c105201b192d229f6abd5827e2ee7e672a05/app/Http/Controllers/Api/Client/Servers/FileController.php#L82-L85\nThough as the actual purpose is not conveyed part of the JWT tokens, this introduces this vulnerability of being able to do non-intended actions due to the expected fields (i.e. `server_uuid`) on most endpoints being the same when parsing it on wings' side. \n\n### PoC\nCreate a new subuser that has the minimal amount of permissions on a server (`websocket.connect`). As that subuser, retrieve a websocket JWT token from the `GET /api/client/servers/[...]/websocket` endpoint (in my case, I manually just make a request under that user's browser session; you can probably just resend the /websocket request in browser console to get a fresh unused token). Using that websocket token, we can abuse this by directly using it in the `/upload/file` endpoint of the wings node instead of using it for websocket authentication:\n```python3\nimport requests\n\nwings_url = 'http://[...]:8080'\nwebsocket_token = '[...]'\n\nres = requests.post(f'{wings_url}/upload/file', params = {\n 'token': websocket_token,\n}, files = {\n 'files': ('file-upload.txt', b'Hello, World!'),\n})\nprint(res.status_code, res.content)\n```\nObserve, that even though our subuser never has permissions outside viewing the console, they are able to write arbitrary files in the server. This pattern happens in a lot of other action, but this is probably the most interesting one.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "pterodactyl/panel"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.12.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/pterodactyl/wings"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.12.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/pterodactyl/panel/security/advisories/GHSA-8r6w-3qq5-4p4r"
}, {
"type" : "WEB",
"url" : "https://github.com/pterodactyl/panel/pull/5636"
}, {
"type" : "WEB",
"url" : "https://github.com/pterodactyl/panel/commit/7ffcd636310bb72b54bac3280d2a15e727feded7"
}, {
"type" : "WEB",
"url" : "https://github.com/pterodactyl/wings/commit/d0ddc80844479302abdaf9654de3bacd511c0f5c"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/pterodactyl/panel"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1259", "CWE-1270" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-28T15:43:25Z",
"nvd_published_at" : null
}
}