REDHAT-BUG-2490024: High severity npm/undici vulnerability

Published Jun 17, 2026
·
Updated

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 Software

3 affected components
npm/undici>7.23.0<=8.1.0
npm/undici<7.26.0
npm/undici<8.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 7.26.0
  2. Upgrade

    Upgrade undici to a version that resolves this vulnerability.

    Fixed in 8.2.0
  3. Configuration

    Use a separate Socks5ProxyAgent instance per origin (instead of sharing a single agent/dispatcher across multiple origins) to avoid cross-origin request routing.

    undici/Socks5ProxyAgent connection_pool_origin_binding = per-origin
  4. Compensating control

    Avoid using Socks5ProxyAgent with multiple origins (e.g., route each origin separately or use a proxy mechanism that preserves origin-to-pool mapping).

Event History

Jun 17, 2026
Data Sourced
via Red Hat·07:04 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2490024?

The severity of REDHAT-BUG-2490024 is classified as high with a score of 7.

2

How do I fix REDHAT-BUG-2490024?

To fix REDHAT-BUG-2490024, ensure you update to a patched version of npm/undici that resolves the connection pool issue.

3

What impact does REDHAT-BUG-2490024 have on my application?

REDHAT-BUG-2490024 can lead to unintended data exposure or manipulation due to improper handling of connections across different origins.

4

Is REDHAT-BUG-2490024 necessary to address immediately?

Yes, due to its high severity, REDHAT-BUG-2490024 should be addressed immediately to mitigate potential security risks.

5

What software is affected by REDHAT-BUG-2490024?

The software affected by REDHAT-BUG-2490024 is npm/undici.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203