# CVE-2026-73232: ffuf denial of service (OOM) via HTTP response decompression bomb


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-73232, GHSA-jcvh-xf52-2cwm, GO-2026-6369, UBUNTU-CVE-2026-73232

## What is CVE-2026-73232?

CVE-2026-73232 is a high-severity vulnerability in ffuf, published on 11 Aug 2026. 

### Official description

ffuf is a fast web fuzzer written in Go. Prior to 2.2.0, ffuf allows a malicious target server to cause an out-of-memory denial of service because the response size guard in pkg/runner/simple.go checks only the compressed Content-Length while io.ReadAll reads gzip, brotli, deflate, transparently decompressed, or chunked response bodies without a decompressed-size bound. This issue is fixed in version 2.2.0.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

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

6 open source packages ship an affected version, including github.com/ffuf/ffuf and github.com/ffuf/ffuf/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ffuf/ffuf` | Go | All versions | None |
| `github.com/ffuf/ffuf` | Go | All versions to 1.5.0 | None |
| `github.com/ffuf/ffuf` | Go | All versions to 1.5.0 | None |
| `github.com/ffuf/ffuf/v2` | Go | All versions | 2.2.0 |
| `github.com/ffuf/ffuf/v2` | Go | All versions | 2.2.0 |
| `github.com/ffuf/ffuf/v2` | Go | All versions | 2.2.0 |

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

Upgrade to a fixed version.

## Is CVE-2026-73232 being exploited?

There is no known exploitation of CVE-2026-73232 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73232 is a high-severity vulnerability in ffuf, published on 11 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-73232 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ffuf/ffuf (Go): affected all versions; no fix listed
- github.com/ffuf/ffuf (Go): affected all versions up to 1.5.0; no fix listed
- github.com/ffuf/ffuf (Go): affected all versions up to 1.5.0; no fix listed
- github.com/ffuf/ffuf/v2 (Go): affected all versions; fixed in 2.2.0
- github.com/ffuf/ffuf/v2 (Go): affected all versions; fixed in 2.2.0
- github.com/ffuf/ffuf/v2 (Go): affected all versions; fixed in 2.2.0

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-73232/ (Markdown: https://insights.sbomify.com/CVE-2026-73232/index.md)
```

## Sources

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

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