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 77% 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
Trending — Patch released this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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.8(medium)
EPSS
23.3%
KEV
Not listed

Published

June 17, 2026

Last Modified

July 6, 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(6)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
undici—8.2.0—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 38× in last 7d / 104× 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 104 total refreshes for this CVE.

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

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 in the National Vulnerability Database on June 17, 2026, with the most recent update on July 6, 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 23.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6734, 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-6734

Explore →

Is Your Infrastructure Affected by CVE-2026-6734?

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

Start Free Scan →Browse All CVEs