CVE-2026-6734

undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse

HIGH
8.8
CVSS Score
Published: June 17, 2026 at 04:36 PM UTC
Updated: September 10, 2026 at 01:20 PM UTC
6 products affected across 3 vendorsUndiciOpenShift AIOpenShift Pipelines

Using undici by undici?

Get instant alerts when new vulnerabilities affect undici - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

7.23.0 ≤ v < 7.28.08.0.0 ≤ v < 8.2.0
Affected range stops below 7.28.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.0, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 1787121387 (unaffected)
Vendor states this is fixed in 1787801527 (unaffected)
7.23.0 ≤ v < 7.26.08.0.0 ≤ v < 8.2.07.23.08.0.0
Vendor states this is fixed in 7.26.0 (unaffected)
Vendor states this is fixed in 8.2.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (23)

Vendor Advisory
Source: cverecord
https://cna.openjsf.org/security-advisories.html
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:22380
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:22934
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:7378
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-6734
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2490024

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-346CWE-940

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card