Response splitting via unsanitized outbound header values
Published Apr 2, 2026 · Updated Apr 2, 2026
HTTP response splitting in Vladislav Shakitskiy's ewe before 3.0.6 allows remote attackers to inject HTTP response content. The encode_headers function writes header keys and values directly into raw response bytes without rejecting embedded carriage returns or line feeds. Exploitation requires an application to place attacker-controlled data in a response header, enabling injected headers or a second response and associated cache poisoning or cross-site scripting.
Summary
What happened
HTTP response splitting in Vladislav Shakitskiy's ewe before 3.0.6 allows remote attackers to inject HTTP response content. The encode_headers function writes header keys and values directly into raw response bytes without rejecting embedded carriage returns or line feeds. Exploitation requires an application to place attacker-controlled data in a response header, enabling injected headers or a second response and associated cache poisoning or cross-site scripting.
The record
- CVE
- CVE-2026-34715
- Published
- Apr 2, 2026
- Updated
- Apr 2, 2026
- Vendor
- Vladislav Shakitskiy
- Product
- ewe
- Classifications
- CWE-113, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2026CVE publishedPublication date reported by the CVE source.
- Apr 2, 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.0.6
What conditions does exploitation require?
What is affected?
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
- GHSA-x2w3-23jr-hrpf response-header injection proof of conceptproof of concept · demonstrated
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