Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73232 high CVSS 7.5

Vulnerability in github.com/ffuf/ffuf/v2 (CVE-2026-73232)

Summary

Vulnerability in github.com/ffuf/ffuf/v2 (CVE-2026-73232). Risk of unauthorized operations or information disclosure. Exploitable via io.ReadAll. Mitigation: upgrade to 2.2.0 or later.

Original description

The description as published by the source.

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 and the already-decoded body is read unbounded.
  2. brotli/deflate (or gzip with headers preserved): Content-Length reflects the small compressed size and passes the check; the body is then manually decompressed into an unbounded
    io.ReadAll.
  3. chunked transfer encoding: no Content-Length header is present, so the numeric parse fails and the check is skipped entirely.

Impact

Denial of service against the operator running ff…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73232 has been found in github.com/ffuf/ffuf/v2.
Attackers can target a specific entry point like io.ReadAll over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/ffuf/ffuf/v2 to 2.2.0 or later.
If unsure, ask your IT team or search "github.com/ffuf/ffuf/v2 CVE-2026-73232" on the vendor's site.

CVE-2026-73232 (github.com/ffuf/ffuf/v2) — CWE-409 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: io.ReadAll / io.LimitReader
Patched: 2.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-409) exists in github.com/ffuf/ffuf/v2. Attackers reach the vulnerable code path via io.ReadAll without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/ffuf/ffuf/v2. Attack surface: io.ReadAll / io.LimitReader.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.2.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ffuf/ffuf/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/ffuf/ffuf/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/ffuf/ffuf/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/ffuf/ffuf/v2 to 2.2.0

    ステージング環境で 2.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/ffuf/ffuf/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.0"}]}]
go github.com/ffuf/ffuf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details