CRLF Injection Affecting npm package, versions <1:11.11.0-1.24.14.1.2.module+el8.10.0+24190+49a46c75


Severity

Recommended
high

Based on CentOS security rating.

Threat Intelligence

EPSS
0.01% (2nd 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-CENTOS8-NPM-15633861
  • published15 Mar 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 Centos:8 npm to version 1:11.11.0-1.24.14.1.2.module+el8.10.0+24190+49a46c75 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream npm package and not the npm package as distributed by Centos. See How to fix? for Centos:8 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