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.4%, 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
Trending — 4 sources updated 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
28.3%
KEV
Not listed

Published

June 17, 2026

Last Modified

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

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
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
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.

Data Freshness Timeline

(refreshed 14× in last 7d / 106× 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 126 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database on June 17, 2026, with the most recent update on July 21, 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 28.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