urllib3 vulnerabilities
HTTP library with thread-safe connection pooling, file post, and more.
- Registry
- PyPI
- Latest
- 2.8.0
- License
- MIT
22 known advisories
The latest version, 2.8.0, is not affected by any of them. Projects on older versions may be.
pip install 'urllib3>=2.8.0'Is your project on an affected urllib3?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for urllib3
urllib3: Chunked Deflate streaming can enter an infinite loop
- Affected
- >=2.6.2 <2.8.0
- Fixed in
- 2.8.0
urllib3: HTTPResponse.stream()/read_chunked() buffers an unbounded chunk-size line into memory
- Affected
- >=1.10.3 <2.8.0
- Fixed in
- 2.8.0
urllib3: HTTPS proxy TLS configuration may be ignored or overridden
- Affected
- >=1.26.0 <2.8.0
- Fixed in
- 2.8.0
urllib3: Decompression-bomb safeguards bypassed in parts of the streaming API
- Affected
- >=2.6.0 <2.7.0
- Fixed in
- 2.7.0
urllib3: Sensitive headers forwarded across origins in proxied low-level redirects
- Affected
- >=1.23 <2.7.0
- Fixed in
- 2.7.0
Decompression-bomb safeguards bypassed when following HTTP redirects (streaming API)
- Affected
- >=1.22 <2.6.3
- Fixed in
- 2.6.3
urllib3 streaming API improperly handles highly compressed data
- Affected
- >=1.0 <2.6.0
- Fixed in
- 2.6.0
urllib3 allows an unbounded number of links in the decompression chain
- Affected
- >=1.24 <2.6.0
- Fixed in
- 2.6.0
urllib3 does not control redirects in browsers and Node.js
- Affected
- >=2.2.0 <2.5.0
- Fixed in
- 2.5.0
urllib3 redirects are not disabled when retries are disabled on PoolManager instantiation
- Affected
- <2.5.0
- Fixed in
- 2.5.0
urllib3's Proxy-Authorization request header isn't stripped during cross-origin redirects
- Affected
- <1.26.19 · >=2.0.0 <2.2.2
- Fixed in
- 1.26.19, 2.2.2
urllib3's request body not stripped after redirect from 303 status changes request method to GET
- Affected
- >=2.0.0 <2.0.7 · <1.26.18
- Fixed in
- 1.26.18, 2.0.7
Authorization Header forwarded on redirect
- Affected
- <1.24.2
- Fixed in
- 1.24.2
`Cookie` HTTP header isn't stripped on cross-origin redirects
- Affected
- >=2.0.0 <2.0.6 · <1.26.17
- Fixed in
- 1.26.17, 2.0.6
Urllib3 Incorrect Certificate Validation
- Affected
- >=1.17 <1.18.1
- Fixed in
- 1.18.1
Improper Neutralization of CRLF Sequences in urllib3 library for Python
- Affected
- <1.24.3
- Fixed in
- 1.24.3
CRLF injection in urllib3
- Affected
- <1.25.9
- Fixed in
- 1.25.9
Catastrophic backtracking in URL authority parser when passed URL containing many @ characters
- Affected
- >=1.25.4 <1.26.5
- Fixed in
- 1.26.5
Uncontrolled Resource Consumption in urllib3
- Affected
- >=1.25.2 <1.25.8
- Fixed in
- 1.25.8
Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection
- Affected
- >=1.26.0 <1.26.4
- Fixed in
- 1.26.4
Improper Certificate Validation in urllib3
- Affected
- <1.24.2
- Fixed in
- 1.24.2
Exposure of Sensitive Information to an Unauthorized Actor in urllib3
- Affected
- <1.23
- Fixed in
- 1.23
Is your urllib3 version vulnerable?
- urllib3 2.8No known advisories in 2.8.0
- urllib3 2.73 advisories in 2.7.0
- urllib3 2.65 advisories in 2.6.3
- urllib3 2.56 advisories in 2.5.0
- urllib3 2.48 advisories in 2.4.0
- urllib3 2.38 advisories in 2.3.0
- urllib3 1.267 advisories in 1.26.20
- urllib3 1.2510 advisories in 1.25.11
- urllib3 1.2410 advisories in 1.24.3
- urllib3 1.2312 advisories in 1.23.0
- urllib3 1.2212 advisories in 1.22.0
- urllib3 1.2111 advisories in 1.21.1
- urllib3 0.29 advisories in 0.2.0
Which of your client projects still run an old urllib3?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.