Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

ffuf denial of service (OOM) via HTTP response decompression bomb

CVE-2026-73232GHSA-jcvh-xf52-2cwm

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/ffuf/ffuf/v2

    Affected
    <= 2.1.0
    Fixed in
    2.2.0

  • Go github.com/ffuf/ffuf

    Affected
    <= 1.5.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-73232: 0.63% estimated exploitation activity in the next 30 days; percentile 50.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A malicious or attacker-controlled target server can crash ffuf with an out-of-memory condition by returning a compressed HTTP response that decompresses to a very large body (a decompression bomb). This works against default usage with no special flags.

Details The response body size guard in pkg/runner/simple.go only checks the server-supplied Content-Length header, which reflects the compressed size and is absent for chunked responses or when Go's net/http transport transparently decompresses the body. After that check, io.ReadAll reads the entire decompressed stream into memory with no upper bound, so a small compressed body that expands to gigabytes causes unbounded allocation and the process is terminated by the OS OOM killer. The guard is bypassed in three independent ways: 1. gzip (default configuration): the transport requests gzip on its own and transparently decompresses the response, stripping Content-Encoding and Content-Length, so the size check is skipped…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jcvh-xf52-2cwm

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6369

  3. Revision 1 · created ·

    Published from osv record GHSA-jcvh-xf52-2cwm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73232

Advisory: ffuf denial of service (OOM) via HTTP response decompression bomb
IDs: CVE-2026-73232, GHSA-jcvh-xf52-2cwm
Record: https://patchnext.com/advisories/cve-2026-73232 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/ffuf/ffuf/v2 2.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ffuf/ffuf/v2: affected <= 2.1.0; fixed in 2.2.0
- Go github.com/ffuf/ffuf: affected <= 1.5.0

## Suggested inspection (read-only)
- Go github.com/ffuf/ffuf/v2: check the installed version with your package manager.
- Go github.com/ffuf/ffuf: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ffuf/ffuf/v2, github.com/ffuf/ffuf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jcvh-xf52-2cwm (OSV record GHSA-jcvh-xf52-2cwm lists affected ranges: Go github.com/ffuf/ffuf/v2 >=0 =0 <=1.5.0)
- Verified: https://osv.dev/vulnerability/GO-2026-6369 (OSV record GO-2026-6369 lists affected ranges: Go github.com/ffuf/ffuf >=0; Go github.com/ffuf/ffuf/v2 >=0 <2.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jcvh-xf52-2cwm (GitHub-reviewed advisory GHSA-jcvh-xf52-2cwm lists affected ranges: Go github.com/ffuf/ffuf/v2 >=0 =0 <=1.5.0)

Commands are suggestions: review each one before running it.

Loading voting…