# CVE-2026-61617: Pterodactyl Wings SFTP write path does not enforce disk quota, allowing node-wide disk exhaustion

> Attackers with SFTP access can exhaust host disk space by bypassing quota checks, causing denial of service for all servers on the node.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-8j54-xcwx-597p

## What is CVE-2026-61617?

CVE-2026-61617 is a high-severity denial of service vulnerability in pterodactyl wings, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wings is the server control plane for the Pterodactyl game-server management panel. In versions up to and including 1.13.2, the SFTP write path does not enforce a server's disk quota during a transfer, allowing a tenant with SFTP write access to a single server to exhaust the host node's physical disk and take down every server on it. Wings checks available space only once, as a boolean, when the write handle is opened, using a stale cached usage value and without knowing the size of the incoming data, and it then returns a raw, unaccounted file handle that is never re-checked as the transfer proceeds. A single upload can therefore be written without bound, far beyond the configured disk limit, until the node's disk is full, and because a server stopped for exceeding its limit is not treated as suspended, SFTP writes are still accepted even after the quota is already exceeded. This issue is fixed in version 1.13.3.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-61617?


## How do I fix CVE-2026-61617?

No fix has been published for CVE-2026-61617 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61617 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61617 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61617 and fix it if it is affected.

What it is: CVE-2026-61617 is a high-severity denial of service vulnerability in pterodactyl wings, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61617 exists.

Affected product: pterodactyl wings. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61617/ (Markdown: https://insights.sbomify.com/CVE-2026-61617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61617
- OSV: https://osv.dev/vulnerability/CVE-2026-61617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61617/
Summaries are generated and may contain mistakes; the official description above is the record.