Response splitting and service interruption via header injection
Published May 8, 2026 · Updated May 8, 2026
HTTP response splitting in i18next-http-middleware before 3.9.3 allows remote attackers to inject headers via a crafted language value. The middleware passes the detected value through an HTML encoder that preserves control characters, then supplies it to res.setHeader as Content-Language. Exposure requires a raw detected value; older Node.js accepts the injected header, while newer Node.js throws an uncaught error that interrupts service.
Summary
What happened
HTTP response splitting in i18next-http-middleware before 3.9.3 allows remote attackers to inject headers via a crafted language value. The middleware passes the detected value through an HTML encoder that preserves control characters, then supplies it to res.setHeader as Content-Language. Exposure requires a raw detected value; older Node.js accepts the injected header, while newer Node.js throws an uncaught error that interrupts service.
The record
- CVE
- CVE-2026-41683
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- i18next
- Product
- i18next-http-middleware
- Classifications
- CWE-113, CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=< 3.9.3
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