Is urllib3 2.7 vulnerable?

PyPI · 1 release from 2.7.0 to 2.7.0 · latest urllib3 is 2.8.0 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. urllib3 2.7.0, the last 2.7 release, is affected by 3 known security advisories (2 high, 1 medium), including CVE-2026-97689, CVE-2026-97687, CVE-2026-97688. Upgrade to 2.8.0 or later to fix all of them.

Upgrade with:pip install 'urllib3>=2.8.0'

Is your project on an affected urllib3?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting urllib3 2.7.0

  • MediumCVE-2026-97688GHSA-gh4c-6fx4-qh6g30 Sept 2026

    urllib3: Chunked Deflate streaming can enter an infinite loop

    Affected
    >=2.6.2 <2.8.0
    Fixed in
    2.8.0
  • HighCVE-2026-97689GHSA-vxq7-64xx-v4gw30 Sept 2026

    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
  • HighCVE-2026-97687GHSA-8988-9cw3-xx7730 Sept 2026

    urllib3: HTTPS proxy TLS configuration may be ignored or overridden

    Affected
    >=1.26.0 <2.8.0
    Fixed in
    2.8.0

Which of your client projects are still on urllib3 2.7?

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.