CVE-2026-84382: HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
Summary When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded. Details HTTPX2's default transport reads the socket in pieces of up to 64 KiB.
Published Sep 8, 2026
Affected packages
httpx2
- Ecosystem
- PyPI
- Affected
- < 2.12.0
- Fixed in
- 2.12.0
- Check
pip show httpx2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When decoding a compressed response body (gzip, deflate, br, or zstd), HTTPX2 fully decompressed each network read before yielding content to the application. A small compressed input could therefore cause a large intermediate memory allocation, even when the application streamed the response to keep memory usage bounded.
Details
HTTPX2's default transport reads the socket in pieces of up to 64 KiB. Before 2.12.0, each piece was inflated completely into one intermediate allocation before any decompressed bytes were yielded.
At DEFLATE's maximum compression ratio of roughly 1032:1, a 64 KiB compressed chunk can expand to about 64 MiB in one allocation. Brotli and Zstandard responses can cause similarly large amplification. Streaming the response did not prevent these transient allocations.
Impact
Applications that fetch resources from untrusted or attacker-influenced servers - such as webhook receivers, link unfurlers, crawlers, SSRF-reachable fetchers, and redirect followers - can experience memory pressure or out-of-memory termination when processing a malicious compressed response. No authentication or user interaction is required beyond issuing a request to the server.
Mitigation
Upgrade to HTTPX2 2.12.0 or later. Patched versions decompress responses incrementally with bounded intermediate buffers, including responses with multiple content encodings.
Credited to tawAsh1.
References
- https://github.com/pydantic/httpx2/security/advisories/GHSA-8xx6-hgc6-gc2m
- https://nvd.nist.gov/vuln/detail/CVE-2026-84382
- https://github.com/pydantic/httpx2/pull/1126
- https://github.com/pydantic/httpx2/commit/4fd0c70a3f207c618b145934792f791bccfb39f8
- https://github.com/pydantic/httpx2/releases/tag/v2.12.0
- https://github.com/advisories/GHSA-8xx6-hgc6-gc2m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-84378
HTTPX2: Quadratic SSE line buffering can cause CPU denial of service
medium5.9Sep 8, 2026CVE-2026-84379
HTTPX2: Multipart part header injection via unvalidated file Content-Type and custom headers
medium5.3Sep 8, 2026CVE-2026-84380
HTTPX2: Conflicting Content-Length and Transfer-Encoding headers can be auto-generated
medium5.6Sep 8, 2026CVE-2026-84381
HTTPX2: Secure WebSocket traffic sent without TLS through SOCKS proxies
high8.1Sep 8, 2026
