CVE-2026-61609: CWE-770: Allocation of Resources Without Limits or Throttling in pterodactyl panel
Pterodactyl is a free, open-source game server management panel. From 1.7.0 until 1.13.0, the authentication rate limiter defined in RouteServiceProvider::configureRateLimiting() applied a single global bucket to the login and two-factor checkpoint endpoints instead of keying by IP or account: the fall-through Limit::perMinute(10) covering POST /auth/login and POST /auth/login/checkpoint omitted ->by(), so Laravel derived a constant cache key (md5('authentication')) shared by every request. An unauthenticated attacker sending roughly ten requests per minute from a single IP, most cheaply against the checkpoint endpoint (which has no reCAPTCHA), exhausts the shared counter and causes HTTP 429 for every user attempting to log in or complete two-factor authentication, a panel-wide authentication denial of service that also locks out administrators. This issue is fixed in version 1.13.0.
AI Analysis
Technical Summary
The Pterodactyl panel's authentication rate limiter, in versions 1.7.0 through 1.12.x, applies a single global rate limit bucket to POST /auth/login and POST /auth/login/checkpoint endpoints without keying by IP or user account. This is due to the omission of the ->by() method in Laravel's rate limiter configuration, resulting in a constant cache key shared by all requests. An attacker can send approximately ten requests per minute from a single IP to exhaust this shared limit, causing HTTP 429 responses for all users and effectively locking out legitimate login and two-factor authentication attempts. This vulnerability is classified as CWE-770 (Allocation of Resources Without Limits or Throttling) and leads to a panel-wide authentication denial of service. The vulnerability is resolved in Pterodactyl panel version 1.13.0.
Potential Impact
An unauthenticated attacker can cause a denial of service on the Pterodactyl panel's authentication system by exhausting the global rate limit bucket shared across all login and two-factor authentication requests. This results in HTTP 429 Too Many Requests responses for all users, preventing legitimate login and two-factor authentication attempts, including those by administrators. There is no impact on confidentiality or integrity, but availability of the authentication service is severely affected.
Mitigation Recommendations
This vulnerability is fixed in Pterodactyl panel version 1.13.0. Users should upgrade to version 1.13.0 or later to remediate this issue. No official patch or temporary fix is indicated in the advisory. Until upgrading, consider implementing additional rate limiting keyed by IP or account at a network or application firewall level to mitigate the risk.
CVE-2026-61609: CWE-770: Allocation of Resources Without Limits or Throttling in pterodactyl panel
Description
Pterodactyl is a free, open-source game server management panel. From 1.7.0 until 1.13.0, the authentication rate limiter defined in RouteServiceProvider::configureRateLimiting() applied a single global bucket to the login and two-factor checkpoint endpoints instead of keying by IP or account: the fall-through Limit::perMinute(10) covering POST /auth/login and POST /auth/login/checkpoint omitted ->by(), so Laravel derived a constant cache key (md5('authentication')) shared by every request. An unauthenticated attacker sending roughly ten requests per minute from a single IP, most cheaply against the checkpoint endpoint (which has no reCAPTCHA), exhausts the shared counter and causes HTTP 429 for every user attempting to log in or complete two-factor authentication, a panel-wide authentication denial of service that also locks out administrators. This issue is fixed in version 1.13.0.
CVSS v3.1
Score 7.5high
Affected software
pterodactyl
panel
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Pterodactyl panel's authentication rate limiter, in versions 1.7.0 through 1.12.x, applies a single global rate limit bucket to POST /auth/login and POST /auth/login/checkpoint endpoints without keying by IP or user account. This is due to the omission of the ->by() method in Laravel's rate limiter configuration, resulting in a constant cache key shared by all requests. An attacker can send approximately ten requests per minute from a single IP to exhaust this shared limit, causing HTTP 429 responses for all users and effectively locking out legitimate login and two-factor authentication attempts. This vulnerability is classified as CWE-770 (Allocation of Resources Without Limits or Throttling) and leads to a panel-wide authentication denial of service. The vulnerability is resolved in Pterodactyl panel version 1.13.0.
Potential Impact
An unauthenticated attacker can cause a denial of service on the Pterodactyl panel's authentication system by exhausting the global rate limit bucket shared across all login and two-factor authentication requests. This results in HTTP 429 Too Many Requests responses for all users, preventing legitimate login and two-factor authentication attempts, including those by administrators. There is no impact on confidentiality or integrity, but availability of the authentication service is severely affected.
Mitigation Recommendations
This vulnerability is fixed in Pterodactyl panel version 1.13.0. Users should upgrade to version 1.13.0 or later to remediate this issue. No official patch or temporary fix is indicated in the advisory. Until upgrading, consider implementing additional rate limiting keyed by IP or account at a network or application firewall level to mitigate the risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T17:36:04.597Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a68d75f9c2644c7f8e050ba
Added to database: 07/28/2026, 16:22:55 UTC
Last enriched: 07/29/2026, 18:52:38 UTC
Last updated: 09/12/2026, 22:01:35 UTC
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.