CVE-2026-35202 is a low-severity allocation of resources without limits or throttling vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.3. It is fixed in 1.12.3.
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.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
composer
pterodactyl/panel (< 1.12.3)pterodactyl/panel → 1.12.3 (composer)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-35202 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-35202 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-35202 in your environment →Upgrade pterodactyl/panel to 1.12.3 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-35202 is a low-severity allocation of resources without limits or throttling vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.3. It is fixed in 1.12.3. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
pterodactyl/panel (composer) versions < 1.12.3 is affected.
Yes. CVE-2026-35202 is fixed in 1.12.3. Upgrade to this version or later.
Whether CVE-2026-35202 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
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.
Upgrade pterodactyl/panel to 1.12.3 or later.