CVE-2026-61609: Pterodactyl/panel Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-xvc3-826v-xf47
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2026-61609 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Pterodactyl/panel libraries in the Packagist ecosystem. The issue involves pterodactyl's shared global rate-limit key on login and 2fa checkpoint enables unauthenticated panel-wide authentication lockout (dos). Remediation is available by upgrading affected packages to version 1.13.0.

CVE-2026-61609 at a Glance

CVE Identifier CVE-2026-61609
GHSA Identifier GHSA-xvc3-826v-xf47
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Pterodactyl/panel
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-61609

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.13.0
Upgrade pterodactyl/panel to 1.13.0
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-61609, 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.13.0), 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-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. 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 `authentication` rate limiter used for the login and two-factor checkpoint endpoints applies a single global bucket shared by every client, instead of keying per IP or per account. An unauthenticated attacker sending ~10 requests per minute from one IP exhausts the shared bucket and causes HTTP 429 for every user on every IP attempting to log in or complete 2FA, for as long as the attack is sustained. This is a trivially triggered, unauthenticated, panel-wide authentication denial of service. ### Details In `app/Providers/RouteServiceProvider::configureRateLimiting()` the limiter is defined as: ```php RateLimiter::for('authentication', function (Request $request) { if ($request->route()->named('auth.post.forgot-password')) { return Limit::perMinute(2)->by($request->ip()); } return Limit::perMinute(10); }); ``` The forgot-password branch is correctly scoped with `->by($request->ip())`. The fall-through return, which covers `POST /auth/login` and `POST /auth/login/checkpoint` (see `routes/auth.php`, the `throttle:authentication` group), omits `->by()` entirely. For a named limiter, Laravel 11 derives the cache key as `md5($limiterName . $limit->key)` (`Illuminate\Routing\Middleware\ThrottleRequests::handleRequestUsingNamedLimiter`). `Limit::perMinute(10)` is constructed with an empty `key`, so the resolved key is `md5('authentication')`, a constant identical for every incoming request. All clients therefore contend for one shared counter rather than one counter per source. Two factors make this worse: - `throttle:authentication` is registered as group middleware in `routes/auth.php`, so it increments before the route-level `recaptcha` middleware on `POST /auth/login`. Requests count toward the limit regardless of reCAPTCHA outcome. - `POST /auth/login/checkpoint` has no reCAPTCHA at all, giving an attacker a clean, low-cost way to fill the shared bucket with malformed requests. Once the 10/minute global limit is hit, the throttle returns 429 to all subsequent requests on those endpoints until the one-minute window decays. Repeating the burst each minute holds the panel in a permanent locked-out state for all legitimate users. ### PoC 1. Stand up a default Pterodactyl panel. 2. From a single attacker IP, exhaust the shared bucket via the checkpoint endpoint (no reCAPTCHA): ```bash for i in $(seq 1 11); do curl -s -o /dev/null -w "%{http_code}\n" \ -X POST https://panel.example.com/auth/login/checkpoint \ -H 'Content-Type: application/json' \ -H 'X-Requested-With: XMLHttpRequest' \ -d '{"confirmation_token":"x","authentication_code":"000000"}' done ``` Requests 1-10 return a normal 4xx (validation/auth failure); request 11 returns `429 Too Many Requests`. 3. From a completely different IP and a valid account, attempt a normal login: ```bash curl -s -o /dev/null -w "%{http_code}\n" \ -X POST https://panel.example.com/auth/login \ -H 'Content-Type: application/json' \ -H 'X-Requested-With: XMLHttpRequest' \ -d '{"user":"valid@example.com","password":"correct-horse"}' ``` This returns `429` despite being a different IP, different account, and valid credentials. Looping step 2 once per minute keeps every user locked out indefinitely. ### Impact This is an unauthenticated availability attack against authentication. Any internet-facing Pterodactyl panel can be made unusable for all users (login and 2FA verification both blocked) by a single low-bandwidth attacker, with no credentials, no privileges, and no user interaction. Administrators are locked out alongside regular users, hampering incident response. The forgot-password endpoint is unaffected because it is correctly keyed per IP. Suggested fix: key the fall-through limit by request source, at minimum: ```php return Limit::perMinute(10)->by($request->ip()); ``` Ideally combine the IP with the submitted identifier for login (e.g. `->by($request->ip() . '|' . (string) $request->input('user'))`) and the IP plus confirmation token for the checkpoint, so brute-force protection per account is preserved while removing the shared global bucket. ### Disclaimer This report was written by AI, the bug itself was found and confirmed by the reporter.

CVE-2026-61609 Affected Pterodactyl/panel Versions

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

References

Frequently Asked Questions

What is CVE-2026-61609?
CVE-2026-61609 is a security vulnerability in Pterodactyl/panel involving Pterodactyl's shared global rate-limit key on login and 2FA checkpoint enables unauthenticated panel-wide authentication lockout (DoS) under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Pterodactyl/panel versions are affected?
Affected versions include releases prior to 1.13.0 across affected packages: pterodactyl/panel.
What version fixes CVE-2026-61609?
Upgrading to 1.13.0 (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.13.0. Upgrade your dependency to 1.13.0 or later.
What is the CVSS score of CVE-2026-61609?
CVE-2026-61609 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-61609?
CVE-2026-61609 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Packagist dependencies for CVE-2026-61609?
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-xvc3-826v-xf47",
  "modified" : "2026-07-28T14:57:59Z",
  "published" : "2026-07-28T14:57:59Z",
  "aliases" : [ "CVE-2026-61609" ],
  "summary" : "Pterodactyl's shared global rate-limit key on login and 2FA checkpoint enables unauthenticated panel-wide authentication lockout (DoS)",
  "details" : "### Summary\nThe `authentication` rate limiter used for the login and two-factor checkpoint endpoints applies a single global bucket shared by every client, instead of keying per IP or per account. An unauthenticated attacker sending ~10 requests per minute from one IP exhausts the shared bucket and causes HTTP 429 for every user on every IP attempting to log in or complete 2FA, for as long as the attack is sustained. This is a trivially triggered, unauthenticated, panel-wide authentication denial of service.\n\n### Details\nIn `app/Providers/RouteServiceProvider::configureRateLimiting()` the limiter is defined as:\n\n```php\nRateLimiter::for('authentication', function (Request $request) {\n    if ($request->route()->named('auth.post.forgot-password')) {\n        return Limit::perMinute(2)->by($request->ip());\n    }\n\n    return Limit::perMinute(10);\n});\n```\n\nThe forgot-password branch is correctly scoped with `->by($request->ip())`. The fall-through return, which covers `POST /auth/login` and `POST /auth/login/checkpoint` (see `routes/auth.php`, the `throttle:authentication` group), omits `->by()` entirely.\n\nFor a named limiter, Laravel 11 derives the cache key as `md5($limiterName . $limit->key)` (`Illuminate\\Routing\\Middleware\\ThrottleRequests::handleRequestUsingNamedLimiter`). `Limit::perMinute(10)` is constructed with an empty `key`, so the resolved key is `md5('authentication')`, a constant identical for every incoming request. All clients therefore contend for one shared counter rather than one counter per source.\n\nTwo factors make this worse:\n- `throttle:authentication` is registered as group middleware in `routes/auth.php`, so it increments before the route-level `recaptcha` middleware on `POST /auth/login`. Requests count toward the limit regardless of reCAPTCHA outcome.\n- `POST /auth/login/checkpoint` has no reCAPTCHA at all, giving an attacker a clean, low-cost way to fill the shared bucket with malformed requests.\n\nOnce the 10/minute global limit is hit, the throttle returns 429 to all subsequent requests on those endpoints until the one-minute window decays. Repeating the burst each minute holds the panel in a permanent locked-out state for all legitimate users.\n\n### PoC\n1. Stand up a default Pterodactyl panel.\n2. From a single attacker IP, exhaust the shared bucket via the checkpoint endpoint (no reCAPTCHA):\n\n```bash\nfor i in $(seq 1 11); do\n  curl -s -o /dev/null -w \"%{http_code}\\n\" \\\n    -X POST https://panel.example.com/auth/login/checkpoint \\\n    -H 'Content-Type: application/json' \\\n    -H 'X-Requested-With: XMLHttpRequest' \\\n    -d '{\"confirmation_token\":\"x\",\"authentication_code\":\"000000\"}'\ndone\n```\n\nRequests 1-10 return a normal 4xx (validation/auth failure); request 11 returns `429 Too Many Requests`.\n\n3. From a completely different IP and a valid account, attempt a normal login:\n\n```bash\ncurl -s -o /dev/null -w \"%{http_code}\\n\" \\\n  -X POST https://panel.example.com/auth/login \\\n  -H 'Content-Type: application/json' \\\n  -H 'X-Requested-With: XMLHttpRequest' \\\n  -d '{\"user\":\"valid@example.com\",\"password\":\"correct-horse\"}'\n```\n\nThis returns `429` despite being a different IP, different account, and valid credentials. Looping step 2 once per minute keeps every user locked out indefinitely.\n\n### Impact\nThis is an unauthenticated availability attack against authentication. Any internet-facing Pterodactyl panel can be made unusable for all users (login and 2FA verification both blocked) by a single low-bandwidth attacker, with no credentials, no privileges, and no user interaction. Administrators are locked out alongside regular users, hampering incident response. The forgot-password endpoint is unaffected because it is correctly keyed per IP.\n\nSuggested fix: key the fall-through limit by request source, at minimum:\n\n```php\nreturn Limit::perMinute(10)->by($request->ip());\n```\n\nIdeally combine the IP with the submitted identifier for login (e.g. `->by($request->ip() . '|' . (string) $request->input('user'))`) and the IP plus confirmation token for the checkpoint, so brute-force protection per account is preserved while removing the shared global bucket.\n\n### Disclaimer\nThis report was written by AI, the bug itself was found and confirmed by the reporter.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "pterodactyl/panel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.7.0"
      }, {
        "fixed" : "1.13.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.12.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pterodactyl/panel/security/advisories/GHSA-xvc3-826v-xf47"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pterodactyl/panel"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T14:57:59Z",
    "nvd_published_at" : null
  }
}