CRLF Injection Affecting nodejs24 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.25% (16th 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-17293683
  • published11 Jun 2026
  • disclosed3 Jun 2026

Introduced: 3 Jun 2026

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

How to fix?

There is no fixed version for RHEL:10 nodejs24.

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.

Impact: The morgan logging middleware's :remote-user token extracts the Basic auth username from the Authorization request header and writes it to the log stream without neutralizing control characters. An unauthenticated attacker can send a crafted Authorization Basic header containing CR or LF bytes to inject forged log lines, breaking the one-request-per-line structure of access logs and enabling log forgery against downstream log consumers. The built-in combined, common, default, and short formats are affected, as well as any custom format that references :remote-user. Affected versions: morgan 1.2.0 through 1.10.1. Patches: upgrade to morgan 1.11.0, which neutralizes control characters in the :remote-user token output. Workarounds: use a custom format string that does not include :remote-user.

CVSS Base Scores

version 3.1