# Pterodactyl improperly locks resources allowing raced queries to create more resources than alloted

Advisory record · `GHSA-jw2v-cq5x-q68g`

- **Identifiers:** `GHSA-jw2v-cq5x-q68g` · `CVE-2025-69198` · `PKSA-hm8z-9vp5-kfyz`
- **State:** Confirmed
- **Severity:** CVSS 6.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-362](https://cwe.mitre.org/data/definitions/362.html) · [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-413](https://cwe.mitre.org/data/definitions/413.html) · [CWE-667](https://cwe.mitre.org/data/definitions/667.html)
- **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md) · [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-413](https://agentprime.io/advisories/tag/cwe-413.md) · [CWE-667](https://agentprime.io/advisories/tag/cwe-667.md)
- **Published:** 20 Jan 2026
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Jan 2026, 16:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pterodactyl/panel` (Packagist): affected `<1.12.0`; fixed in `1.12.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Pterodactyl panel versions before 1.12.0 are vulnerable to a race condition in resource limit checks. An authenticated user who sends many requests at the same time can create more databases, port allocations, or backups for a server than its configured limit allows, which can exhaust node allocations and backup space. Upgrade to Pterodactyl panel 1.12.0 or later.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.0 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jw2v-cq5x-q68g)

## Sources

- [GitHub Advisory Database: GHSA-jw2v-cq5x-q68g](https://github.com/advisories/GHSA-jw2v-cq5x-q68g)
- [OSV: GHSA-jw2v-cq5x-q68g](https://osv.dev/vulnerability/GHSA-jw2v-cq5x-q68g)
- <https://github.com/pterodactyl/panel/security/advisories/GHSA-jw2v-cq5x-q68g>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-69198>
- <https://github.com/pterodactyl/panel/commit/09caa0d4995bd924b53b9a9e9b4883ac27bd5607>
- <https://github.com/pterodactyl/panel>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jw2v-cq5x-q68g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jw2v-cq5x-q68g/>. Everything for agents: <https://agentprime.io/llms.txt>.