HTTP header injection via unvalidated upgrade value
Published Mar 12, 2026 · Updated Mar 12, 2026
CRLF injection in the client.request() upgrade option in Node.js Undici allows remote attackers to inject headers into outbound HTTP/1.1 requests. The HTTP/1.1 dispatcher appends the upgrade value directly to its header buffer without rejecting carriage-return or line-feed characters. Exploitation requires a consuming application to pass attacker-controlled input to client.request(); successful input can end the request and send chosen bytes to a reachable non-HTTP service.
Summary
What happened
CRLF injection in the client.request() upgrade option in Node.js Undici allows remote attackers to inject headers into outbound HTTP/1.1 requests. The HTTP/1.1 dispatcher appends the upgrade value directly to its header buffer without rejecting carriage-return or line-feed characters. Exploitation requires a consuming application to pass attacker-controlled input to client.request(); successful input can end the request and send chosen bytes to a reachable non-HTTP service.
The record
- CVE
- CVE-2026-1527
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- Node.js
- Product
- Undici
- Classifications
- CWE-93
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 2026Record 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=< 6.24.0; 7.0.0 < 7.24.0
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