CVE-2025-23167

published 19 May 2025 · updated 16 Nov 2026

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.

6.5MediumCVSS 6.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 10.*, 11.*, 12.* and 13 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nodejs>=10.0 <10.*, >=11.0 <11.*, >=12.0 <12.*, >=13.0 <13.*, >=14.0 <14.*, >=15.0 <15.*, >=16.0 <16.*, >=17.0 <17.*, >=18.0 <18.*, >=19.0 <19.*, >=20.0 <=20.19.1, >=4.0 <4.*, >=5.0 <5.*, >=6.0 <6.*, >=7.0 <7.*, >=8.0 <8.*, >=9.0 <9.*10.*, 11.*, 12.*, 13.*, 14.*, 15.*, 16.*, 17.*, 18.*, 19.*, 4.*, 5.*, 6.*, 7.*, 8.*, 9.*

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-23167 severity on Zeptric[![CVE-2025-23167](https://zeptric.io/badge/cve/CVE-2025-23167.svg)](https://zeptric.io/cve/CVE-2025-23167)