CVE-2026-6734

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 72% 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, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Impact: When using Socks5ProxyAgent, undici reuses a single connection pool across different origins without verifying that the pool's origin matches the requested origin. All requests are dispatched through the pool connected to the first origin, regardless of the intended destination.

This causes cross-origin request routing: credentials and request data intended for origin B are sent to origin A, responses from the wrong origin are trusted, and HTTPS requests may be silently downgraded to HTTP.

Impacted users are applications that use Socks5ProxyAgent (directly or via setGlobalDispatcher) and make requests to more than one origin.

This was introduced in undici 7.23.0 via PR #4385 and affects all versions through 8.1.0.

Patches: Upgrade to undici v7.26.0 or v8.2.0.

Workarounds: Use a separate Socks5ProxyAgent instance per origin, or avoid using Socks5ProxyAgent with multiple origins.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
30th
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 cross-origin request routing via SOCKS5 proxy pool reuse · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-hm92-r4w5-c3mj
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

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

Vendor Advisories for CVE-2026-6734(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 / 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:17867031432026-08-18redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatcryostat/cryostat-grafana-dashboard-rhel9:4.2.0-132026-07-29redhat
redhatdevspaces/code-rhel9:17852457772026-07-29redhat
redhatrhdh/rhdh-hub-rhel9:17842109212026-07-20redhat
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.2.0: fixed in 8.2.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 33× 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 297 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-6734?
CVE-2026-6734 is a high vulnerability published on June 17, 2026. Impact: When using Socks5ProxyAgent, undici reuses a single connection pool across different origins without verifying that the pool's origin matches the requested origin. All requests are dispatched through the pool connected to the first origin, regardless of the intended destination. This causes…
When was CVE-2026-6734 disclosed?
CVE-2026-6734 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-6734 actively exploited?
CVE-2026-6734 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6734?
CVE-2026-6734 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-6734?
A fix for CVE-2026-6734 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6734 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-6734

Explore →

Is Your Infrastructure Affected by CVE-2026-6734?

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

Book a Demo →Browse All CVEs