CVE-2025-23167 Affecting nodejs-16 package, versions <16.20.2-r15


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.1% (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-CHAINGUARDLATEST-NODEJS16-12597499
  • published10 Sept 2025
  • disclosed19 May 2025

Introduced: 19 May 2025

CVE-2025-23167  (opens in a new tab)

How to fix?

Upgrade Chainguard nodejs-16 to version 16.20.2-r15 or higher.

NVD Description

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

A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using \r\n\rX instead of the required \r\n\r\n. This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests.

The issue was resolved by upgrading llhttp to version 9, which enforces correct header termination.

Impact:

  • This vulnerability affects only Node.js 20.x users prior to the llhttp v9 upgrade.

CVSS Base Scores

version 3.1