CVE-2026-35202: Pterodactyl/panel Remote Code Execution Vulnerability

LOW
Advisory Identifier: GHSA-fgmm-w5cx-vrfw
CWE-367 CWE-770
Published
Advisory Summary

CVE-2026-35202 is a LOW remote code execution vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting Pterodactyl/panel libraries in the Packagist ecosystem. The issue involves pterodactyl has a database resource limit bypass via race condition in client api. Remediation is available by upgrading affected packages to version 1.12.3.

CVE-2026-35202 at a Glance

CVE Identifier CVE-2026-35202
GHSA Identifier GHSA-fgmm-w5cx-vrfw
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
Affected Product Pterodactyl/panel
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix CVE-2026-35202

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.

pterodactyl/panel fixed: 1.12.3
Upgrade pterodactyl/panel to 1.12.3
Verify Direct and Transitive Dependencies

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-35202, 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-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. 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

### Summary The Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything. ### Details Inside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing. Since there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host. ### Impact Users are able to create more databases than they are supposed to, potentially also breaking the web interface.

CVE-2026-35202 Affected Pterodactyl/panel Versions

1 component(s)
Fixed Versions:
1.12.3
Product / Package Ecosystem Affected Versions Fixed Version
pterodactyl/panel
Packagist
< 1.12.3
1.12.3

References

Frequently Asked Questions

What is CVE-2026-35202?
CVE-2026-35202 is a security vulnerability in Pterodactyl/panel involving Pterodactyl has a database resource limit bypass via race condition in Client API under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition.
Which Pterodactyl/panel versions are affected?
Affected versions include releases prior to 1.12.3 across affected packages: pterodactyl/panel.
What version fixes CVE-2026-35202?
Upgrading to 1.12.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pterodactyl/panel affected?
Yes, pterodactyl/panel is affected in releases prior to 1.12.3. Upgrade your dependency to 1.12.3 or later.
What CWE is associated with CVE-2026-35202?
CVE-2026-35202 is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition (The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.).
How can I check Packagist dependencies for CVE-2026-35202?
Run the dependency tree command: 'inspect dependencies for pterodactyl/panel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fgmm-w5cx-vrfw",
  "modified" : "2026-06-09T11:00:09Z",
  "published" : "2026-05-26T19:30:02Z",
  "aliases" : [ "CVE-2026-35202" ],
  "summary" : "Pterodactyl has a database resource limit bypass via race condition in Client API",
  "details" : "### Summary\n\nThe Pterodactyl Client API has a logic flaw that lets users bypass their assigned limits for database allocations. This happens because the database locking mechanism used in the controllers is totally broken and doesn't actually lock anything.\n\n### Details\n\nInside `DatabaseController.php`, the code tries to prevent multiple databases from being created at once by calling `$server->databases()->lockForUpdate()`. In Laravel, this just configures a query builder but never actually sends a command to the database because it’s missing a terminal method like `count()` or `get()`. It’s basically a no-op that does nothing.\n\nSince there’s no real lock, multiple requests hitting the endpoint at the exact same time will all see that the database count is under the limit. They all move forward to the `DeployServerDatabaseService` and successfully create extra resources on the physical host.\n\n### Impact\n\nUsers are able to create more databases than they are supposed to, potentially also breaking the web interface.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "pterodactyl/panel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.12.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pterodactyl/panel/security/advisories/GHSA-fgmm-w5cx-vrfw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35202"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pterodactyl/panel"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-367", "CWE-770" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-26T19:30:02Z",
    "nvd_published_at" : "2026-06-02T20:16:35Z"
  }
}