CRLF Injection Affecting nodejs24 package, versions <1:24.14.1-2.el10_1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.01% (1st 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 Learn

Learn about CRLF Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL10-NODEJS24-16053249
  • published15 Apr 2026
  • disclosed12 Mar 2026

Introduced: 12 Mar 2026

CVE-2026-1527  (opens in a new tab)
CWE-93  (opens in a new tab)

How to fix?

Upgrade RHEL:10 nodejs24 to version 1:24.14.1-2.el10_1 or higher.
This issue was patched in RHSA-2026:7675.

NVD Description

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

ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to:

  • Inject arbitrary HTTP headers
  • Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters:

// lib/dispatcher/client-h1.js:1121 if (upgrade) { header += connection: upgrade\r\nupgrade: ${upgrade}\r\n }

CVSS Base Scores

version 3.1