Request smuggling via bare carriage-return delimiters
Published Jun 30, 2023 · Updated Nov 4, 2025
HTTP request smuggling in Node.js 16, 18, and 20 allows remote attackers to desynchronize HTTP message boundaries via crafted requests. The http module's llhttp parser accepts a bare carriage return, without the required line feed, as the end of an HTTP header field. Exploitation requires an HTTP service to process attacker-controlled traffic in a chain whose other processor interprets the malformed boundary differently, enabling a smuggled request to alter subsequent HTTP handling.
Summary
What happened
HTTP request smuggling in Node.js 16, 18, and 20 allows remote attackers to desynchronize HTTP message boundaries via crafted requests. The http module's llhttp parser accepts a bare carriage return, without the required line feed, as the end of an HTTP header field. Exploitation requires an HTTP service to process attacker-controlled traffic in a chain whose other processor interprets the malformed boundary differently, enabling a smuggled request to alter subsequent HTTP handling.
The record
- CVE
- CVE-2023-30589
- Published
- Jun 30, 2023
- Updated
- Nov 4, 2025
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0 <10.*
- Affected versionversion=11.0 <11.*
- Affected versionversion=12.0 <12.*
- Affected versionversion=13.0 <13.*
- Affected versionversion=14.0 <14.*
- Affected versionversion=15.0 <15.*
- Affected versionversion=16.0 <16.20.1
- Affected versionversion=17.0 <17.*
- Affected versionversion=18.0 <18.16.1
- Affected versionversion=19.0 <19.*
- Affected versionversion=20.0 <20.3.1
- Affected versionversion=4.0 <4.*
- Affected versionversion=5.0 <5.*
- Affected versionversion=6.0 <6.*
- Affected versionversion=7.0 <7.*
- Affected versionversion=8.0 <8.*
- Affected versionversion=9.0 <9.*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo