CVE-2026-6734 Affecting nodejs:24/nodejs-packaging-bundler package, versions <0:2021.06-6.module_el8.10.0+4086+70facd4a


Severity

Recommended
0.0
high
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.35% (27th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX8-NODEJS-17999627
  • published17 Jul 2026
  • disclosed6 Jul 2026

Introduced: 6 Jul 2026

NewCVE-2026-6734  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 nodejs:24/nodejs-packaging-bundler to version 0:2021.06-6.module_el8.10.0+4086+70facd4a or higher.
This issue was patched in ALSA-2026:39868.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:24/nodejs-packaging-bundler package and not the nodejs:24/nodejs-packaging-bundler package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

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 Base Scores

version 3.1