CVE-2026-49755
High 8.2No known exploitationFix availableDecompression bomb DoS in Req via auto-decoded archive and compressed response bodies
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 52% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in wojtekmach Req allows attacker-controlled HTTP servers to exhaust memory in a Req client via decompression-bomb response bodies. Req's default response pipeline includes Req.Steps.decode_body/1 and Req.Steps.decompress_body/1 in lib/req/steps.ex. decode_body/1 dispatches on the server-supplied content-type (or URL extension) and calls :zip.extract(body, [:memory]) for application/zip, :erl_tar.extract({:binary, body}, [:memory]) for application/x-tar, and :erl_tar.extract({:binary, body}, [:memory, :compressed]) for application/gzip / .tgz. Each returns the full decompressed archive contents as a [{name, bytes}] list in memory, with no per-entry or total size cap. decompress_body/1 walks the content-encoding header and chains :zlib/:brotli/:ezstd decoders, so a response advertising content-encoding: gzip, gzip, gzip inflates through multiple layers without bound. Both steps are enabled by default, no caller opt-in is required, and the attacker controls the content-type and content-encoding headers on their own server (or on any host reached via Req's automatic redirect following). A sub-megabyte response can expand to multiple gigabytes on the victim, crashing the BEAM process. This issue affects req: from 0.1.0 before 0.6.1.
Weakness: CWE-409
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- Disable Req's automatic body decoding on requests that fetch attacker-influenced URLs by passing decode_body: false to Req.new/1 / Req.get!/1. To also skip the content-encoding decompression pipeline, pass raw: true. Both options leave the response body as the raw on-the-wire bytes, so the caller can size-check before any decompression. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| wojtekmach | req | from 0.1.0 before 0.6.1 | 0.6.1 | NIST NVD |
| wojtekmach | req | from 0.1.0 before 0.6.1 | 0.6.1 | CVE Program |
| wojtekmach | req | e37753741cbdc725e6aba3d977b380163bfc0ecb | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by NVD (reference tagged Patch)
Vendor guidance and references
- Fix commit 84977e5 in wojtekmach/req (opens in a new tab)patch
- Fix commit ea5506f in wojtekmach/req (opens in a new tab)patch
- Unbounded archive/compression extraction triggered by response content-type (opens in a new tab)vendor-advisory, related
- OSV record EEF-CVE-2026-49755 (opens in a new tab)mitigation, patch, related, third party advisory
- EEF CNA record for CVE-2026-49755 (opens in a new tab)related, third party advisory
- Introducing commit e377537 in wojtekmach/req (opens in a new tab)related