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 62% 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
Trending — Patch released this week
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%CVSS: 7.4Exploit: None knownExposed: 0

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.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 17, 2026

Last Modified

August 20, 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(18)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatcryostat/cryostat-grafana-dashboard-rhel9:4.2.0-132026-07-29redhat
redhatdevspaces/code-rhel9:17852457772026-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
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatdevspaces/pluginregistry-rhel9:17829893672026-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 rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 7.3.0+dfsg1+~cs24.12.11-2 (11 versions)8.5.0+dfsg+~cs3.2.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
undici—8.5.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 113× 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 204 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database on June 17, 2026, with the most recent update on August 20, 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% probability of exploitation in the next 30 days, which ranks it in the top 61.8% of all scored CVEs.
What is the CVSS score of CVE-2026-9697?
CVE-2026-9697 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-9697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9697, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs