Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted file.create permissions

CVE-2026-54593GHSA-8r6w-3qq5-4p4r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pterodactyl/panel 1.12.3; github.com/pterodactyl/wings 1.12.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-54593: 0.68% estimated exploitation activity in the next 30 days; percentile 52.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A 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 serveruuid, useruuid, and uniqueid, 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. Impact Any 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. Details The panel generated JWT tokens for various purposes: -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8r6w-3qq5-4p4r

  2. Revision 1 · created ·

    Published from osv record GO-2026-6120

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54593

Advisory: Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
IDs: CVE-2026-54593, GHSA-8r6w-3qq5-4p4r
Record: https://patchnext.com/advisories/cve-2026-54593 (revision 2, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pterodactyl/panel 1.12.3; github.com/pterodactyl/wings 1.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pterodactyl/panel: affected < 1.12.3; fixed in 1.12.3
- Go github.com/pterodactyl/wings: affected < 1.12.2; fixed in 1.12.2

## Suggested inspection (read-only)
- Packagist pterodactyl/panel: check the installed version with your package manager.
- Go github.com/pterodactyl/wings: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pterodactyl/panel, github.com/pterodactyl/wings.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6120 (OSV record GO-2026-6120 lists affected ranges: Go github.com/pterodactyl/wings >=0 <1.12.2 (fixed))
- Verified: https://github.com/advisories/GHSA-8r6w-3qq5-4p4r (GitHub-reviewed advisory GHSA-8r6w-3qq5-4p4r lists affected ranges: Packagist pterodactyl/panel >=0 =0 <1.12.2)

Commands are suggestions: review each one before running it.

Loading voting…