Is urllib3 2.2 vulnerable?
PyPI · 4 releases from 2.2.0 to 2.2.3 · latest urllib3 is 2.8.0 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. urllib3 2.2.3, the last 2.2 release, is affected by 8 known security advisories (6 high, 2 medium), including CVE-2026-97689, CVE-2026-97687, CVE-2026-44431. 1 more affects earlier 2.2.x releases. Upgrade to 2.8.0 or later to fix all of them.
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
Advisories affecting urllib3 2.2.3
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: 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
Fixed within 2.2.x, affecting earlier releases
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
Every urllib3 2.2.x release
Affected: 2.2.0 to 2.2.3. Latest urllib3: 2.8.0.
| Version | Known advisories |
|---|---|
| urllib3 2.2.3 | CVE-2026-97689, CVE-2026-97687, CVE-2026-44431, CVE-2026-21441, CVE-2025-66471, CVE-2025-66418, CVE-2025-50182, CVE-2025-50181 |
| urllib3 2.2.2 | CVE-2026-97689, CVE-2026-97687, CVE-2026-44431, CVE-2026-21441, CVE-2025-66471, CVE-2025-66418, CVE-2025-50182, CVE-2025-50181 |
| urllib3 2.2.1 | CVE-2026-97689, CVE-2026-97687, CVE-2026-44431, CVE-2026-21441, CVE-2025-66471, CVE-2025-66418, CVE-2025-50182, CVE-2025-50181, CVE-2024-37891 |
| urllib3 2.2.0 | CVE-2026-97689, CVE-2026-97687, CVE-2026-44431, CVE-2026-21441, CVE-2025-66471, CVE-2025-66418, CVE-2025-50182, CVE-2025-50181, CVE-2024-37891 |
Which of your client projects are still on urllib3 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact urllib3 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other urllib3 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.