pterodactyl/panel

CVE-2026-26016

CVE-2026-26016 is a critical-severity security vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.1. It is fixed in 1.12.1.

Key facts
CVSS score
N/A
Critical
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
pterodactyl/panel
Fixed in
1.12.1
Disclosed
2026

Summary

Summary A missing authorization check in multiple controllers allows any user with access to a node secret token to fetch information about any server on a Pterodactyl instance, even if that server is associated with a different node. This issue stems from missing logic to verify that the node requesting server data is the same node that the server is associated with. Any authenticated Wings node can retrieve server installation scripts (potentially containing secret values) and manipulate the installation status of servers belonging to other nodes. Wings nodes may also manipulate the transfer status of servers belonging to other nodes. This vulnerability requires a user to acquire a secret access token for a node. We rated this issue based on potential worst outcome. Unless a user gains access to a Wings secret access token they would not be able to access any of these vulnerable endpoints, as every endpoint requires a valid node access token. Details The Remote API endpoint GET /api/remote/servers/{uuid} fetches a server by UUID and returns its complete configuration without verifying that the requesting node owns the server. Both failure() and success() methods in ServerTransferController fetch servers by UUID without verifying node ownership. Missing authorization checks in ServerInstallController allow any authenticated Wings node to retrieve egg installation scripts (containing deployment secrets) and manipulate the installation status of servers belonging to other nodes. Impact A single compromised Wings node daemon token (stored in plaintext at /etc/pterodactyl/config.yml) grants access to sensitive configuration data of every server on the panel, rather than only to servers that the node has access to. An attacker can use this information to move laterally through the system, send excessive notifications, destroy server data on other nodes, and otherwise exfiltrate secrets that they should not have access to with only a node token. Additionally, triggering a false transfer success causes the panel to delete the server from the source node, resulting in permanent data loss.

Impact

Not available

Affected versions

composer

  • pterodactyl/panel (< 1.12.1)

Security releases

  • pterodactyl/panel → 1.12.1 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-26016 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-26016 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-26016 in your environment

Remediation advice

Upgrade pterodactyl/panel to 1.12.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-26016

What is CVE-2026-26016?

CVE-2026-26016 is a critical-severity security vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.1. It is fixed in 1.12.1.

Which versions of pterodactyl/panel are affected by CVE-2026-26016?

pterodactyl/panel (composer) versions < 1.12.1 is affected.

Is there a fix for CVE-2026-26016?

Yes. CVE-2026-26016 is fixed in 1.12.1. Upgrade to this version or later.

Is CVE-2026-26016 exploitable, and should I be worried?

Whether CVE-2026-26016 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-26016 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-26016?

Upgrade pterodactyl/panel to 1.12.1 or later.

Stop the waste.
Protect your environment with Kodem.