CVE-2026-97687

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-89000 (ENISA EUVD) · GHSA-8988-9cw3-xx77 (GitHub Security Advisories) · PYSEC-2026-4175 (OSV.dev)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 29, 2026

Last Modified

October 13, 2026

Advisory Details (5)

Auto-updated Sep 29, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

2.8.0

Patch available: urllib3/urllib3 2.8.0

https://github.com/urllib3/urllib3/releases/tag/2.8.0
GitHub commit Patch Available

commit b6447295fff7 (urllib3/urllib3)

Patch available: urllib3/urllib3 2.8.0 (contains commit b6447295fff7)

https://github.com/urllib3/urllib3/commit/b6447295fff7b38fdffc67e0df9712d60cef3cc3
GitHub commit Patch Available

commit 07408cec79d1 (urllib3/urllib3)

Patch available: urllib3/urllib3 2.8.0 (contains commit 07408cec79d1)

https://github.com/urllib3/urllib3/commit/07408cec79d1856d81bb42c74a904a24fdb9e465
GitHub pull request Patch Available

HTTPSConnection: Prefer proxy verify policy for the proxy connection

Patch available: urllib3/urllib3 2.8.0 (PR #5093 merged 2026-07-29)

https://github.com/urllib3/urllib3/pull/5093
GitHub advisoryMentions a patch (unverified)

HTTPS proxy TLS configuration may be ignored or overridden · Advisory · urllib3/urllib3 · GitHub

https://github.com/urllib3/urllib3/security/advisories/GHSA-8988-9cw3-xx77

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython3.12-urllib3-0:2.8.0-1.el9pc2026-11-05redhat
redhatpython-urllib3-0:2.8.0-1.el9pc2026-11-05redhat
redhatdiscovery/discovery-ui-rhel9:17937337162026-11-04redhat
redhatcostmanagement/costmanagement-ui-rhel10:17938253182026-11-04redhat
redhatrhtas/rh-sigstore-a2a-rhel9:17936241222026-11-04redhat
redhatpython-urllib3-0:1.26.19-4.el10_2.22026-11-02redhat
redhatpython3.12-urllib3-0:1.26.19-5.el8_102026-10-29redhat
redhatrhoai/rhai-cli-rhel9:17927221772026-10-29redhat
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatsatellite/foreman-mcp-server-rhel9:17932722792026-10-29redhat
redhatsatellite/foreman-mcp-server-rhel9:17932722762026-10-29redhat
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
redhatpython-urllib3-0:1.26.5-8.el9_8.22026-10-26redhat
redhatrhelai3/bootc-rocm-rhel9:17926129212026-10-26redhat
redhatrhelai3/disk-image-cuda-rhel9:17927017962026-10-26redhat
redhatansible-automation-platform-26/lightspeed-rhel9:17918984032026-10-21redhat
redhatansible-automation-platform-27/lightspeed-rhel9:17921413862026-10-21redhat
redhatpython3.12-urllib3-0:1.26.19-3.el9_8.22026-10-20redhat
redhatpython3.14-urllib3-0:2.6.3-2.el9_8.62026-10-19redhat
redhatpython3.14-urllib3-0:2.6.3-2.el10_2.62026-10-19redhat
redhatrhtas/model-transparency-rhel9:17924027392026-10-19redhat
redhatrhaii/vllm-cuda-rhel9:17918571832026-10-14redhat
redhatrhaii/model-opt-cuda-rhel9:17918571102026-10-14redhat
redhatrhaii/vllm-cpu-rhel9:17918573012026-10-14redhat
redhatrhaii/vllm-rocm-rhel9:17918567252026-10-14redhat
redhatrhaii/vllm-spyre-rhel9:17918585922026-10-14redhat
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
pipurllib3 @ 2.8.0 (fixes >= 1.26.0, < 2.8.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib31.26.12-1 ... 2.8.0-2 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib32.3.0-3 ... 2.8.0-2 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-urllib32.3.0-3 ... 2.7.0-3 (9 versions)
  • every version up to 2.8.0-1: fixed in 2.8.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
urllib31.26.0 ... 2.7.0 (46 versions)
  • 1.26.0 up to 2.8.0: fixed in 2.8.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 115 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-11-11 04:03 UTCEchelonGraph re-scored
  5. 2026-11-11 04:03 UTCVendor advisory
  6. 2026-11-11 04:03 UTCGHSA enrichmentGHSA-8988-9cw3-xx77 · GitHub severity HIGH
  7. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-11-10 14:26 UTCEchelonGraph re-scored
  9. 2026-11-10 14:26 UTCVendor advisory
  10. 2026-11-10 14:26 UTCGHSA enrichmentGHSA-8988-9cw3-xx77 · GitHub severity HIGH
  11. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-11-03 20:25 UTCEchelonGraph re-scored
  18. 2026-11-03 20:25 UTCVendor advisory
  19. 2026-11-03 20:25 UTCGHSA enrichmentGHSA-8988-9cw3-xx77 · GitHub severity HIGH
  20. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-11-03 15:49 UTCEchelonGraph re-scored
  22. 2026-11-03 15:49 UTCVendor advisory
  23. 2026-11-03 15:49 UTCGHSA enrichmentGHSA-8988-9cw3-xx77 · GitHub severity HIGH
  24. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 75 more
  1. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-8988-9cw3-xx77 · GitHub severity HIGH
  2. 2026-11-01 07:37 UTCEchelonGraph re-scored
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-27 20:27 UTCEchelonGraph re-scored
  8. 2026-10-27 20:27 UTCVendor advisory
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-25 13:47 UTCEchelonGraph re-scored
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-20 17:41 UTCEchelonGraph re-scored
  17. 2026-10-20 17:41 UTCVendor advisory
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-18 02:56 UTCEchelonGraph re-scored
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-13 20:46 UTCEchelonGraph re-scored▲ 0.50
  26. 2026-10-13 20:46 UTCVendor advisory
  27. 2026-10-13 20:44 UTCNVD updateCVSS v3 → 8.1
  28. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-10-13 04:01 UTCEchelonGraph re-scored
  30. 2026-10-13 04:01 UTCVendor advisory
  31. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-10-12 14:39 UTCEchelonGraph re-scored
  33. 2026-10-11 19:10 UTCEchelonGraph re-scored
  34. 2026-10-11 18:05 UTCVendor advisory
  35. 2026-10-11 16:26 UTCEchelonGraph re-scored
  36. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-10-11 13:38 UTCEchelonGraph re-scored
  38. 2026-10-11 06:44 UTCEchelonGraph re-scored
  39. 2026-10-11 06:44 UTCVendor advisory
  40. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-10-10 19:24 UTCVendor advisory
  42. 2026-10-10 08:05 UTCVendor advisory
  43. 2026-10-09 20:45 UTCEchelonGraph re-scored
  44. 2026-10-09 20:45 UTCVendor advisory
  45. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-10-09 09:27 UTCVendor advisory
  47. 2026-10-08 22:08 UTCEchelonGraph re-scored
  48. 2026-10-08 22:08 UTCVendor advisory
  49. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-10-08 10:49 UTCEchelonGraph re-scored
  51. 2026-10-08 10:49 UTCVendor advisory
  52. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-10-07 23:30 UTCVendor advisory
  54. 2026-10-07 12:12 UTCVendor advisory
  55. 2026-10-07 00:51 UTCEchelonGraph re-scored
  56. 2026-10-07 00:51 UTCVendor advisory
  57. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-10-06 13:18 UTCVendor advisory
  59. 2026-10-06 02:00 UTCEchelonGraph re-scored
  60. 2026-10-06 02:00 UTCVendor advisory
  61. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-10-05 14:40 UTCVendor advisory
  63. 2026-10-05 03:22 UTCEchelonGraph re-scored
  64. 2026-10-05 03:22 UTCVendor advisory
  65. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-10-04 16:03 UTCVendor advisory
  67. 2026-10-04 04:43 UTCVendor advisory
  68. 2026-10-03 17:24 UTCEchelonGraph re-scored
  69. 2026-10-03 17:24 UTCVendor advisory
  70. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  71. 2026-10-03 06:06 UTCVendor advisory
  72. 2026-10-02 18:47 UTCEchelonGraph re-scored
  73. 2026-10-02 18:47 UTCVendor advisory
  74. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  75. 2026-10-02 07:27 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-97687?
CVE-2026-97687 is a high-severity vulnerability; its CVE record was published on September 29, 2026. 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…
When was the CVE record for CVE-2026-97687 published?
The CVE record for CVE-2026-97687 was published on September 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-97687 actively exploited?
CVE-2026-97687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97687?
CVE-2026-97687 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-97687?
A fix for CVE-2026-97687 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97687 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97687

Explore →

Is Your Infrastructure Affected by CVE-2026-97687?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.