Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing
Summary
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. A flaw was found in undici. When using Socks5ProxyAgent, undici incorrectly reuses a single connection pool across different origins. This can lead to cross-origin request routing, where sensitive credentials and data intended for one destination are sent to another. Consequently, responses from unintended origins may be trusted, and secure HTTPS connections could be silently downgraded to unencrypted HTTP, resulting in information disclosure and data integrity issues. This is rated as an Important security flaw. The `undici` library, when configured with `Socks5ProxyAgent` to handle requests for multiple origins, incorrectly reuses connection pools. This can lead to sensitive data and credentials being misrouted to unintended destinations, potentially downgrading HTTPS connections to HTTP and compromising data integrity and confidentiality. Red Hat products utilizing `undici` with `Socks5ProxyAgent` in multi-origin scenarios are affected. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-940. Fixed by RHSA-2026:35841, RHSA-2026:34342, RHSA-2026:22380, RHSA-2026:22934, RHSA-2026:7378 — update the affected packages (`sudo dnf update`). Affected Red Hat products: Red Hat Enterprise Linux 10; Cluster Observability Operator 1.5.0; Red Hat Hardened Images.
- cluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:1782839494
- cluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1782839193
- cluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1782839981
- cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1782840519
- nodejs25-main-25.9.0-1.1.hum1
- nodejs24-1:24.18.0-1.el10_2
- cluster-observability-operator/monitoring-console-plugin-rhel9:1782838476
- rust-main-1.96.0-1.hum1
- cluster-observability-operator/distributed-tracing-console-plugin-rhel9:1782838753
- cluster-observability-operator/monitoring-console-plugin-pf5-rhel9:1782844225
- cluster-observability-operator/monitoring-console-plugin-pf6-rhel9:1782839658
- nodejs26-main-26.3.0-1.2.hum1
Official advisory · high-confidence parse· fetched 5 hours ago·verify at source
- nodejs24-1:24.18.0-1.el10_2
- cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1782840519
- cluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1782839981
- cluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1782839193
- cluster-observability-operator/distributed-tracing-console-plugin-rhel9:1782838753
- cluster-observability-operator/logging-console-plugin-rhel9:1782841925
- cluster-observability-operator/monitoring-console-plugin-pf5-rhel9:1782844225
- cluster-observability-operator/monitoring-console-plugin-pf6-rhel9:1782839658
- cluster-observability-operator/monitoring-console-plugin-rhel9:1782838476
- cluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:1782839494
- nodejs26-main-26.3.0-1.2.hum1
- rust-main-1.96.0-1.hum1
- nodejs25-main-25.9.0-1.1.hum1
- RHSA-2026:35841
- RHSA-2026:34342
- RHSA-2026:22380
- RHSA-2026:22934
- RHSA-2026:7378
Official advisory · high-confidence parse· fetched 5 hours ago·verify at source
Mitigation checklist
- The single most impactful mitigation is applying network egress controls to restrict which external destinations affected applications can reach. Because the vulnerability causes requests to be misrouted to wrong origins, limiting the set of reachable origins directly reduces the attack surface. These controls collectively limit the blast radius of the connection pool misrouting — the attacker must compromise one of the explicitly allowed destinations rather than any arbitrary origin — but they do not fix the underlying logic bug.
Official advisory · high-confidence parse· fetched 5 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.