CVE-2026-9697

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Impact: undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert, key, rejectUnauthorized, and servername settings.

Applications that pin to an internal or corporate CA via requestTls.ca will, when their proxy URI is SOCKS5, get the default Mozilla CA bundle as the trust anchor instead. Any cert signed by any publicly-trusted CA for the target hostname is accepted, breaking the intended pin and enabling MITM read and tamper of the HTTPS exchange.

Affected applications are those that use undici's ProxyAgent (or Socks5ProxyAgent directly) with SOCKS5 AND rely on requestTls for TLS scope restriction. The bug was introduced in undici 7.23.0 when SOCKS5 support was added.

Patches: Upgrade to undici v7.28.0 or v8.5.0.

Workarounds: No workaround is available within the SOCKS5 path. If a SOCKS5 proxy with TLS scope restriction is required and an upgrade is not yet possible, route the traffic through an HTTP-proxy ProxyAgent instead, where requestTls is honored correctly.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

Published

June 17, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github.
github Patch Available

undici vulnerable to TLS certificate validation bypass via dropped requestTls in SOCKS5 ProxyAgent · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-vmh5-mc38-953g
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-9697(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17847448592026-08-06redhat
redhatdevspaces/code-rhel9:17852457772026-07-29redhat
redhatcryostat/cryostat-grafana-dashboard-rhel9:4.2.0-132026-07-29redhat
redhatrhdh/rhdh-hub-rhel9:17842109212026-07-20redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17833063962026-07-16redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs24-main-24.18.0-0.3.hum12026-07-11redhat
redhatdevspaces/pluginregistry-rhel9:17829893672026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:17828394942026-07-01redhat
redhatrust-main-1.96.0-1.hum12026-06-03redhat
redhatnodejs26-main-26.3.0-1.2.hum12026-06-02redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat

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

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 7.3.0+dfsg1+~cs24.12.11-2 (11 versions)
  • every version up to 8.5.0+dfsg+~cs3.2.0-1: fixed in 8.5.0+dfsg+~cs3.2.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 7.23.0 up to 7.28.0: fixed in 7.28.0
  • 8.0.0 up to 8.5.0: fixed in 8.5.0
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 9× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 283 total refreshes for this CVE.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-03 06:09 UTCOSV refresh
  4. 2026-10-02 17:57 UTCEPSS rescore
  5. 2026-10-01 19:51 UTCEPSS rescore
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-29 15:24 UTCEPSS rescore
  8. 2026-09-28 13:52 UTCEPSS rescore
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-27 13:49 UTCEPSS rescore
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-24 14:04 UTCEPSS rescore
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-22 16:01 UTCEPSS rescore
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-17 19:32 UTCEPSS rescore
  19. 2026-09-16 14:09 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 03:06 UTCEG score recompute
  23. 2026-09-14 03:06 UTCVendor advisory
  24. 2026-09-13 16:48 UTCEPSS rescore
  25. 2026-09-13 14:12 UTCEG score recompute
Show 75 more
  1. 2026-09-13 14:12 UTCVendor advisory
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:38 UTCEPSS rescore
  5. 2026-09-10 13:38 UTCEG score recompute
  6. 2026-09-10 13:38 UTCVendor advisory
  7. 2026-09-10 12:25 UTCEG score recompute
  8. 2026-09-10 12:25 UTCVendor advisory
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-09 13:39 UTCEG score recompute
  11. 2026-09-09 13:39 UTCVendor advisory
  12. 2026-09-09 12:37 UTCEG score recompute
  13. 2026-09-09 12:37 UTCVendor advisory
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 13:29 UTCEG score recompute
  18. 2026-09-04 13:29 UTCVendor advisory
  19. 2026-09-04 12:20 UTCEG score recompute
  20. 2026-09-04 12:20 UTCVendor advisory
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-31 13:31 UTCEG score recompute
  26. 2026-08-31 13:31 UTCVendor advisory
  27. 2026-08-31 12:30 UTCEG score recompute
  28. 2026-08-31 12:30 UTCVendor advisory
  29. 2026-08-30 21:19 UTCEG score recompute
  30. 2026-08-30 21:19 UTCVendor advisory
  31. 2026-08-30 19:18 UTCEPSS rescore
  32. 2026-08-30 01:22 UTCEPSS rescore
  33. 2026-08-28 21:42 UTCEPSS rescore
  34. 2026-08-28 16:46 UTCEG score recompute
  35. 2026-08-28 16:46 UTCVendor advisory
  36. 2026-08-28 15:59 UTCEG score recompute
  37. 2026-08-28 15:59 UTCVendor advisory
  38. 2026-08-27 14:25 UTCEPSS rescore
  39. 2026-08-26 14:47 UTCEPSS rescore
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-25 01:49 UTCEG score recompute
  42. 2026-08-25 01:49 UTCVendor advisory
  43. 2026-08-24 14:18 UTCEPSS rescore
  44. 2026-08-24 13:29 UTCEG score recompute
  45. 2026-08-24 13:29 UTCVendor advisory
  46. 2026-08-24 12:20 UTCEG score recompute
  47. 2026-08-24 12:20 UTCVendor advisory
  48. 2026-08-24 05:19 UTCVendor advisory
  49. 2026-08-23 16:32 UTCVendor advisory
  50. 2026-08-23 04:11 UTCEG score recompute
  51. 2026-08-23 04:11 UTCVendor advisory
  52. 2026-08-23 00:19 UTCEPSS rescore
  53. 2026-08-21 23:49 UTCEPSS rescore
  54. 2026-08-21 14:39 UTCVendor advisory
  55. 2026-08-21 02:18 UTCEG score recompute
  56. 2026-08-21 02:18 UTCVendor advisory
  57. 2026-08-20 22:56 UTCEPSS rescore
  58. 2026-08-20 13:57 UTCEG score recompute
  59. 2026-08-20 13:57 UTCVendor advisory
  60. 2026-08-20 12:42 UTCEG score recompute
  61. 2026-08-20 12:42 UTCVendor advisory
  62. 2026-08-20 08:13 UTCEG score recompute
  63. 2026-08-20 08:13 UTCVendor advisory
  64. 2026-08-19 17:04 UTCEPSS rescore
  65. 2026-08-19 12:25 UTCEG score recompute
  66. 2026-08-19 12:25 UTCVendor advisory
  67. 2026-08-19 12:09 UTCEG score recompute
  68. 2026-08-19 12:09 UTCVendor advisory
  69. 2026-08-19 08:09 UTCEG score recompute
  70. 2026-08-19 08:09 UTCVendor advisory
  71. 2026-08-18 13:49 UTCEPSS rescore
  72. 2026-08-17 13:47 UTCEPSS rescore
  73. 2026-08-17 10:52 UTCVendor advisory
  74. 2026-08-16 22:32 UTCEG score recompute
  75. 2026-08-16 22:32 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-9697?
CVE-2026-9697 is a high vulnerability published on June 17, 2026. Impact: undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert, key, rejectUnauthorized, and…
When was CVE-2026-9697 disclosed?
CVE-2026-9697 was first published on June 17, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9697 actively exploited?
CVE-2026-9697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9697?
CVE-2026-9697 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9697?
A fix for CVE-2026-9697 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9697 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-9697

Explore →

Is Your Infrastructure Affected by CVE-2026-9697?

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

Book a Demo →Browse All CVEs