CVE-2025-66471: urllib3 streaming API improperly handles highly compressed data
Impact urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd).
Published Dec 5, 2025 · Updated Sep 25, 2026
Affected packages
urllib3
- Ecosystem
- PyPI
- Affected
- >= 1.0, < 2.6.0
- Fixed in
- 2.6.0
- Check
pip show urllib3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.
When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.
The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.
Affected usages
Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.
stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.
Remediation
Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.
If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.
Credits
The issue was reported by @Cycloctane. Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.
Credited to illia-v, pquentin, sethmlarson, Cycloctane, stamparm, Chi-Song-Owen.
References
- https://github.com/urllib3/urllib3/security/advisories/GHSA-2xpw-w6gg-jr37
- https://github.com/urllib3/urllib3/commit/c19571de34c47de3a766541b041637ba5f716ed7
- https://nvd.nist.gov/vuln/detail/CVE-2025-66471
- https://github.com/urllib3/urllib3/commit/d0fde3672e4a4093f7587858dccfc298eb66e46c
- https://github.com/advisories/GHSA-2xpw-w6gg-jr37
- https://github.com/pypa/advisory-database/tree/main/vulns/urllib3/PYSEC-2026-1994.yaml
- https://github.com/urllib3/urllib3
- https://pypi.org/project/urllib3
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-97687
urllib3: HTTPS proxy TLS configuration may be ignored or overridden
high7.6Sep 30, 2026CVE-2026-97688
urllib3: Chunked Deflate streaming can enter an infinite loop
medium6.9Sep 30, 2026CVE-2026-97689
urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory
high8.9Sep 30, 2026CVE-2026-44431
urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
high5.3May 11, 2026CVE-2026-44432
urllib3: Decompression-bomb safeguards bypassed in parts of the streaming API
high7.5May 11, 2026CVE-2026-21441
Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
high7.5Jan 7, 2026
