urllib3 Flaw CVE-2026-97687: Update Now
Published October 28, 2026 · Last updated October 28, 2026
The short version: CVE-2026-97687 is a high-severity security flaw in urllib3. The National Vulnerability Database (NVD) published it on September 29, 2026, and the score it lists is 8.1 out of 10. When FraudMeNot checked on October 28, 2026, CISA had not added CVE-2026-97687 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-97687
The record was filed by github.com. In its own words: "urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, and CERT_NONE configuration paths fail to remain separated because target-server TLS settings are incorrectly applied to the HTTPS proxy connection. The trigger is that an application uses an HTTPS proxy and configures target-server TLS settings that must remain separate from the proxy TLS handshake, including HTTPS forwarding with target-specific identity or credentials. Applying cert_reqs=CERT_NONE can overwrite proxy_ssl_context.verify_mode in place, and the mutation persists so later connections reusing the same context may connect to the HTTPS proxy without certificate verification. The attack mechanism is that an attacker intercepts and impersonates the HTTPS proxy after the effective proxy policy accepts the attacker's certificate. The impact is that the attacker can observe or modify forwarded traffic or receive a target TLS client certificate, while CONNECT tunneling still preserves the separate end-to-end target TLS connection. This issue is fixed in version 2.8.0."
Why urllib3 admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on nist.gov rated CVE-2026-97687 8.1 (High) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; a user has to take an action, such as opening a file or link. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping urllib3 running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.
Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on github.com gives it 7.6 (High, CVSS 4.0).
Affected urllib3 releases
According to the record, these releases are vulnerable:
- version >= 1.26.0, < 2.8.0
The type of bug behind CVE-2026-97687
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-295, Improper Certificate Validation. MITRE describes this class of bug as follows: "The product does not validate, or incorrectly validates, a certificate."
- CWE-440, Expected Behavior Violation. MITRE describes this class of bug as follows: "A feature, API, or function does not perform according to its specification."
Vendor remediation for CVE-2026-97687
The vendor advisory remediation for operators of urllib3, quoted for this page, is: "Upgrade urllib3 to version 2.8.0 or later (for example, pip install --upgrade 'urllib3>=2.8.0'), then rebuild any containers or virtual environments that pin an older copy. The flaw only matters for apps that send traffic through an HTTPS proxy with separate target-server TLS settings, but upgrading everywhere is the simplest fix."
What to do about it
- Update now: Upgrade urllib3 to version 2.8.0 or later (for example, pip install --upgrade 'urllib3>=2.8.0'), then rebuild any containers or virtual environments that pin an older copy. The flaw only matters for apps that send traffic through an HTTPS proxy with separate target-server TLS settings, but upgrading everywhere is the simplest fix.
- Who should act: IT teams, managed service providers, and developers who run or ship urllib3. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from urllib3 (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from September 29, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-97687. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-97687 record details from CISA and NVD
- Attack complexity for CVE-2026-97687: low
- CVE-2026-97687 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-97687: exploitability 2.8, impact 5.2.
- Who mapped the weakness type: the address listed on github.com (Secondary)
- NVD product identifiers (CPE):
cpe:2.3:a:python:urllib3:*:*:*:*:*:*:*:* - References in the NVD record: 5 (3 tagged Patch, 1 tagged Issue Tracking, 1 tagged Release Notes).
- CISA SSVC decision points for CVE-2026-97687 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- September 29, 2026: NVD publishes CVE-2026-97687.
- October 28, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-97687 is not listed.
- October 13, 2026: most recent NVD update (record status: Analyzed).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- github.com/urllib3/urllib3/commit/07408cec79d1856d81bb42c74a904a24fdb9e465 (Patch)
- github.com/urllib3/urllib3/commit/b6447295fff7b38fdffc67e0df9712d60cef3cc3 (Patch)
- github.com/urllib3/urllib3/pull/5093 (Issue Tracking, Patch)
- github.com/urllib3/urllib3/releases/tag/2.8.0 (Release Notes)
- github.com/urllib3/urllib3/security/advisories/GHSA-8988-9cw3-xx77 (Vendor Advisory)
Sources
- NVD: CVE-2026-97687
- CVE.org: CVE-2026-97687
- urllib3 advisory
- urllib3 advisory
- urllib3 advisory
- MITRE CWE-295
- MITRE CWE-440
General education only, not security advice. Facts checked against the sources above on the date shown.