Low

Pterodactyl has a database resource limit bypass via race condition in Client API

  • Disclosed: 26.05.2026
  • Updated: 11.10.2026 10:22

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package pterodactyl/panel < 1.12.3 1.12.3

References

CVSS score -
CVSS vector
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
Weakness (CWE)
CWE-367, CWE-770
Platform
Composer
Package
pterodactyl/panel
Disclosed
26.05.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-fgmm-w5cx-vrfw - CC BY 4.0

Vulnerability history: pterodactyl/panel

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (19) in the archive
Total entries
19
First → latest
10.2020 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 6
  • Medium 8
  • Low 3

Disclosures per year

  1. 2020: 1
  2. 2021: 3
  3. 2022: 2
  4. 2023: 0
  5. 2024: 2
  6. 2025: 2
  7. 2026: 9
Severity:
  1. Pterodactyl has a database resource limit bypass via race condition in Client API this entry
    Low CVE-2026-35202 < 1.12.3 1.12.3
  2. Critical · 10.0 CVE-2025-49132 < 1.11.11 1.11.11
  3. High · 7.5 CVE-2019-1020002 < 0.7.14 0.7.14

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.