Advisory

GHSA-fgmm-w5cx-vrfw

Also known as: CVE-2026-35202

Summary

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

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-05-26 19:30 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

pterodactyl/panel

Packagist · All systems

Affected

  • introduced 0, fixed 1.12.3 (ecosystem)

Fixed versions

1.12.3

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences