CVE-2026-49755

Decompression bomb DoS in Req via auto-decoded archive and compressed response bodies

HIGH
7.5
CVSS Score
Published: June 8, 2026 at 03:20 PM UTC
Updated: August 18, 2026 at 04:05 PM UTC
1 product affected across 1 vendorReq

Using req by wojtekmach?

Get instant alerts when new vulnerabilities affect req - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.1.0 ≤ v < 0.6.10.1.0e37753741cbdc725e6aba3d977b380163bfc0ecb
Vendor states this is fixed in 84977e5b1a83f26e749d55ad06e3625464af4e8d (fixed)
Affected range stops below 0.6.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

Vendor AdvisoryRelatedExploitPatch
Source: cverecord
https://github.com/wojtekmach/req/security/advisories/GHSA-655f-mp8p-96gv
RelatedThird Party Advisory
Source: cverecord
https://cna.erlef.org/cves/CVE-2026-49755.html
RelatedThird Party AdvisoryPatchMitigation
Source: cverecord
https://osv.dev/vulnerability/EEF-CVE-2026-49755

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-409

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card