CVE-2026-6734
Received Received - Intake
BaseFortify

Publication date: 2026-06-17

Last updated on: 2026-06-17

Assigner: openjs

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-17
Last Modified
2026-06-17
Generated
2026-06-17
AI Q&A
2026-06-17
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
nodejs undici From 7.23.0 (inc) to 8.1.0 (inc)
nodejs undici 7.26.0
nodejs undici 8.2.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability affects the undici library, specifically when using Socks5ProxyAgent. The issue is that undici reuses a single connection pool across different origins without verifying that the pool's origin matches the requested destination. As a result, requests intended for one origin may be sent through the connection pool of another origin.

This causes cross-origin request routing, meaning credentials and request data meant for one origin can be sent to a different origin. Additionally, responses from the wrong origin may be trusted, and HTTPS requests might be silently downgraded to HTTP, compromising security.

Impact Analysis

If your application uses Socks5ProxyAgent (directly or via setGlobalDispatcher) and makes requests to multiple origins, this vulnerability can cause sensitive data such as credentials and request information to be sent to unintended origins.

This can lead to exposure of confidential information, trust in incorrect responses, and potential downgrading of secure HTTPS requests to insecure HTTP, which increases the risk of data interception or manipulation.

Overall, it impacts the confidentiality, integrity, and availability of your application's communications.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade the undici library to version 7.26.0 or 8.2.0.

Alternatively, you can use a separate Socks5ProxyAgent instance for each origin instead of reusing a single instance across multiple origins.

Avoid using Socks5ProxyAgent with multiple origins if upgrading is not immediately possible.

Compliance Impact

This vulnerability causes cross-origin request routing, where credentials and request data intended for one origin may be sent to another origin. This can lead to unauthorized exposure of sensitive data.

Such unauthorized data exposure can impact compliance with data protection regulations like GDPR and HIPAA, which require strict controls on the confidentiality and integrity of personal and sensitive information.

Additionally, the vulnerability may silently downgrade HTTPS requests to HTTP, weakening transport security and further risking data confidentiality and integrity.

Detection Guidance

This vulnerability arises from the undici library versions 7.23.0 through 8.1.0 when using Socks5ProxyAgent, which reuses a single connection pool across different origins without verifying the origin. Detection involves identifying if your application uses undici within the affected version range and employs Socks5ProxyAgent (directly or via setGlobalDispatcher) to make requests to multiple origins.

To detect the vulnerability on your system, you can:

  • Check the installed version of undici in your Node.js environment using the command: npm list undici
  • Search your codebase for usage of Socks5ProxyAgent or setGlobalDispatcher to see if multiple origins are targeted.
  • Monitor network traffic for unexpected cross-origin requests or suspicious routing of requests through a single proxy connection.

There are no specific commands provided in the resources for automated detection of this vulnerability, but the above steps can help identify potential exposure.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-6734. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart