https://feed.craftedsignal.io/tags/pterodactyl/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 28 Jul 2026 15:44:29 +0000https://feed.craftedsignal.io/briefs/2026-07-pterodactyl-jwt-scoping/Tue, 28 Jul 2026 15:44:29 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-pterodactyl-jwt-scoping/A privilege escalation vulnerability, CVE-2026-54593, exists in Pterodactyl's Wings component that allows authenticated subusers to upload arbitrary files to a server without explicit file creation permissions, due to insufficient validation of panel-signed JSON Web Tokens (JWTs.A significant privilege escalation vulnerability, tracked as CVE-2026-54593, affects Pterodactyl Panel versions prior to 1.12.3 and Pterodactyl Wings versions prior to 1.12.2. The flaw resides in the Wings /upload/file endpoint, which improperly validates panel-signed JSON Web Tokens (JWTs). Specifically, Wings accepts any valid JWT containing server_uuid, user_uuid, and unique_id, irrespective of the token's intended purpose. This design flaw enables an authenticated subuser, even one with minimal permissions (e.g., only websocket.connect), to reuse a JWT issued for a lower-privilege operation (like WebSocket authentication or file downloads) to upload arbitrary files to the associated server. This bypasses the intended file.create permission checks, allowing unauthorized write access to the server's file system. This vulnerability affects anyone running vulnerable versions of the Pterodactyl game server management software.

Attack Chain

1. An authenticated subuser gains minimal access to a Pterodactyl server, such as the ability to connect to the server's console (requiring websocket.connect permission).
2. The subuser makes an API request to a legitimate low-privilege endpoint on the Pterodactyl Panel, such as /api/client/servers/[...]/websocket or a file download endpoint, to obtain a panel-signed JSON Web Token (JWT).
3. The Pterodactyl Panel issues a JWT containing claims like server_uuid, user_uuid, and unique_id, which are used for various operations across the Panel and Wings.
4. The subuser intercepts and extracts this JWT.
5. The subuser then crafts an HTTP POST request to the Pterodactyl Wings /upload/file endpoint, including the obtained JWT as a query parameter (?token=).
6. The subuser includes arbitrary file content within the POST request, intending to upload it to the server.
7. The Pterodactyl Wings component, due to improper JWT scoping validation, accepts the JWT as valid for file upload, despite the token initially being issued for a different, lower-privilege action.
8. Wings proceeds to write the arbitrary file content to the server's file system, achieving unauthorized file upload and privilege escalation for the subuser.

Impact

This vulnerability allows any authenticated subuser, regardless of their specific permissions on a server, to upload arbitrary files to that server. While the attacker must already have subuser access to the target server, this flaw significantly escalates their privileges beyond what is explicitly granted, potentially leading to unauthorized data modification, execution of malicious scripts, or further system compromise. The impact is confined to the specific server the subuser has access to; users without any subuser access cannot exploit this vulnerability. The inability to properly control file uploads can lead to data integrity issues, denial of service through disk exhaustion, or remote code execution if the uploaded files are executed by vulnerable services on the server.

Recommendation

• Patch CVE-2026-54593: Upgrade Pterodactyl Panel to version 1.12.3 or newer, and Pterodactyl Wings to version 1.12.2 or newer immediately to mitigate CVE-2026-54593.
• Deploy the Sigma rule: Implement the provided Sigma rule in your SIEM to detect suspicious file upload attempts on the Pterodactyl Wings /upload/file endpoint. Tune this rule by identifying and allowlisting legitimate uses of this endpoint.
• Enable webserver logging: Ensure detailed webserver access logs are enabled for your Pterodactyl Wings instance to capture HTTP requests, including method, URI, query parameters, and status codes, which are crucial for detecting this activity.

]]>highthreatprivilege-escalationvulnerabilityJWTPterodactylweb-serverhttps://feed.craftedsignal.io/briefs/2026-07-pterodactyl-dos/Tue, 28 Jul 2026 15:02:20 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-pterodactyl-dos/An unauthenticated attacker can exploit CVE-2026-61609, a global rate-limit vulnerability in Pterodactyl Panel versions up to and including 1.12.4, by sending approximately 10 requests per minute to authentication endpoints, leading to a panel-wide denial of service for all legitimate users and administrators attempting to log in or complete 2FA.A critical vulnerability, tracked as CVE-2026-61609, has been identified in Pterodactyl Panel versions 1.7.0 through 1.12.4. This flaw allows an unauthenticated attacker to trigger a panel-wide denial of service (DoS) by exploiting an improperly configured rate limiter on the login and two-factor authentication (2FA) checkpoint endpoints. The authentication rate limiter, intended to prevent brute-force attacks, uses a single global bucket rather than keying per IP address or per account. This means a low-volume attacker, sending as few as 10 requests per minute from a single IP address, can exhaust this shared bucket. Once exhausted, all subsequent login and 2FA attempts by any user, from any IP address, will receive HTTP 429 "Too Many Requests" responses. This effectively locks out all legitimate users and administrators from accessing the panel, crippling its availability without requiring any prior authentication or complex attack techniques.

Attack Chain

1. An attacker identifies an internet-facing Pterodactyl panel running a vulnerable version (1.7.0-1.12.4).
2. The attacker crafts HTTP POST requests targeting the /auth/login/checkpoint or /auth/login endpoints.
3. From a single IP address, the attacker sends approximately 10 requests per minute to these authentication endpoints.
4. Due to the missing ->by($request->ip()) configuration in the RouteServiceProvider, the Pterodactyl panel increments a single, global rate-limit counter for all requests to these endpoints.
5. Upon the 11th request within a minute, the global rate limit is exceeded, causing the panel to return HTTP 429 "Too Many Requests" responses for all subsequent requests to /auth/login and /auth/login/checkpoint.
6. Legitimate users, attempting to log in or complete 2FA, receive HTTP 429 responses regardless of their IP address or correct credentials.
7. The attacker sustains the low-volume rate of 10 requests per minute, perpetually locking out all users and administrators from accessing the Pterodactyl panel.
8. The panel becomes entirely unusable for authentication, resulting in a sustained, unauthenticated, and panel-wide denial of service.

Impact

This vulnerability poses a severe threat to the availability of affected Pterodactyl panels. An unauthenticated, low-bandwidth attacker can render any internet-facing panel inaccessible for all users, including administrators. The impact is a complete denial of service for authentication, meaning no one can log in or perform 2FA verification. This not only disrupts legitimate user access but also prevents administrators from managing the panel, potentially hindering incident response efforts or critical maintenance. The simplicity and low resource requirement for this attack make it highly attractive for adversaries seeking to cause disruption.

Recommendation

• Patch CVE-2026-61609: Immediately update Pterodactyl Panel to a version greater than 1.12.4, which includes the fix for CVE-2026-61609.
• Deploy the Sigma rule: Deploy the "Detect Pterodactyl Panel Global Rate-Limit DoS (CVE-2026-61609)" Sigma rule to your SIEM to detect attempts to exploit CVE-2026-61609 by monitoring webserver logs for HTTP 429 responses on authentication endpoints.
• Monitor webserver logs: Actively monitor webserver logs for POST requests to /auth/login and /auth/login/checkpoint that result in sc-status: 429, especially from multiple distinct source IPs within a short timeframe, as described in the detection rule.

]]>mediumadvisorydenial-of-servicevulnerabilityweb-applicationpterodactyl