CRLF Injection Affecting nodejs26-bin package, versions <0:26.5.1-1.5.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.15% (6th 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-RHEL10-NODEJS26BIN-18557005
  • published6 Aug 2026
  • disclosed29 Jul 2026

Introduced: 29 Jul 2026

NewCVE-2026-15157  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

Upgrade RHEL:10 nodejs26-bin to version 0:26.5.1-1.5.hum1 or higher.
This issue was patched in RHSA-2026:48273.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs26-bin package and not the nodejs26-bin package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.

CVSS Base Scores

version 3.1