pterodactyl/panel

CVE-2025-69198

CVE-2025-69198 is a medium-severity race condition vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.0. It is fixed in 1.12.0.

Key facts
CVSS score
6.5
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
pterodactyl/panel
Fixed in
1.12.0
Disclosed
2025

Summary

Summary Pterodactyl implements rate limits that are applied to the total number of resources (e.g. databases, port allocations, or backups) that can exist for an individual server. These resource limits are applied on a per-server basis, and validated during the request cycle. However, it is possible for a malicious user to send a massive volume of requests at the same time that would create more resources than the server is allotted. This is because the validation occurs early in the request cycle and does not lock the target resource while it is processing. As a result sending a large volume of requests at the same time would lead all of those requests to validate as not using any of the target resources, and then all creating the resources at the same time. As a result a server would be able to create more databases, allocations, or backups than configured. Impact A malicious user is able to deny resources to other users on the system, and may be able to excessively consume the limited allocations for a node, or fill up backup space faster than is allowed by the system.

Impact

What is race condition?

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

Severity and exposure

CVE-2025-69198 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (1.12.0). Upgrading removes the vulnerable code path.

Affected versions

composer

  • pterodactyl/panel (< 1.12.0)

Security releases

  • pterodactyl/panel → 1.12.0 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2025-69198 is reachable in your applications. Explore open-source security for your team.

See if CVE-2025-69198 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2025-69198 in your environment

Remediation advice

Upgrade pterodactyl/panel to 1.12.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2025-69198

What is CVE-2025-69198?

CVE-2025-69198 is a medium-severity race condition vulnerability in pterodactyl/panel (composer), affecting versions < 1.12.0. It is fixed in 1.12.0. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

How severe is CVE-2025-69198?

CVE-2025-69198 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of pterodactyl/panel are affected by CVE-2025-69198?

pterodactyl/panel (composer) versions < 1.12.0 is affected.

Is there a fix for CVE-2025-69198?

Yes. CVE-2025-69198 is fixed in 1.12.0. Upgrade to this version or later.

Is CVE-2025-69198 exploitable, and should I be worried?

Whether CVE-2025-69198 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2025-69198 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-69198?

Upgrade pterodactyl/panel to 1.12.0 or later.

Stop the waste.
Protect your environment with Kodem.