# CVE-2026-54593: Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions

> Authenticated subusers can bypass file creation restrictions and upload arbitrary files by reusing JWTs issued for lower-privilege operations like WebSocket connections.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-8r6w-3qq5-4p4r, GO-2026-6120

## What is CVE-2026-54593?

CVE-2026-54593 is a high-severity missing authorization vulnerability in pterodactyl panel, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pterodactyl 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.

Weakness: CWE-1270 (Generation of Incorrect Security Tokens), CWE-1259 (Improper Restriction of Security Token Assignment)

## Which versions are affected by CVE-2026-54593?

5 open source packages ship an affected version, including pterodactyl/panel and github.com/pterodactyl/wings.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pterodactyl/panel` | Packagist | All versions | 1.12.3 |
| `pterodactyl/panel` | Packagist | All versions | 1.12.3 |
| `github.com/pterodactyl/wings` | Go | All versions | 1.12.2 |
| `github.com/pterodactyl/wings` | Go | All versions | 1.12.2 |
| `github.com/pterodactyl/wings` | Go | All versions | 1.12.2 |

## How do I fix CVE-2026-54593?

Upgrade pterodactyl/panel to 1.12.3 or later.

## Is CVE-2026-54593 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54593 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54593 and fix it if it is affected.

What it is: CVE-2026-54593 is a high-severity missing authorization vulnerability in pterodactyl panel, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54593 exists.

Affected packages and fixed versions:
- pterodactyl/panel (Packagist): affected all versions; fixed in 1.12.3
- pterodactyl/panel (Packagist): affected all versions; fixed in 1.12.3
- github.com/pterodactyl/wings (Go): affected all versions; fixed in 1.12.2
- github.com/pterodactyl/wings (Go): affected all versions; fixed in 1.12.2
- github.com/pterodactyl/wings (Go): affected all versions; fixed in 1.12.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54593/ (Markdown: https://insights.sbomify.com/CVE-2026-54593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54593
- OSV: https://osv.dev/vulnerability/CVE-2026-54593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54593/
Summaries are generated and may contain mistakes; the official description above is the record.