CVE-2026-34715 ewe Has Improper Neutralization of CRLF Sequences in HTTP Headers (HTTP Request/Response Splitting)
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: yes · technical impact: partial
Description
ewe is a Gleam web server. Prior to version 3.0.6, the encode_headers function in src/ewe/internal/encoder.gleam directly interpolates response header keys and values into raw HTTP bytes without validating or stripping CRLF (\r\n) sequences. An application that passes user-controlled data into response headers (e.g., setting a Location redirect header from a request parameter) allows an attacker to inject arbitrary HTTP response content, leading to response splitting, cache poisoning, and possible cross-site scripting. Notably, ewe does validate CRLF in incoming request headers via validate_field_value() in the HTTP/1.1 parser — but provides no equivalent protection for outgoing response headers in the encoder. This issue has been patched in version 3.0.6.
Upgrade path
2 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| hex ewe(Hex) | < 3.0.6 | 3.0.6 | Fixed |
| vshakitskiy ewe | < 3.0.6; = < 3.0.6 | 3.0.6 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| vshakitskiy ewe | = < 3.0.6 | No fix listed |
| hex ewe(Hex) | < 3.0.6 | 3.0.6 |
| vshakitskiy ewe | < 3.0.6 | 3.0.6 |
References
- https://github.com/vshakitskiy/ewe/security/advisories/GHSA-x2w3-23jr-hrpf exploit vendor-advisory
- https://github.com/vshakitskiy/ewe/commit/ce4ff214d32626a10fda9398dc94a2d720e17446 patch
- https://github.com/vshakitskiy/ewe/releases/tag/v3.0.6 product release-notes
- nvd.nist.gov third-party-advisory
- github.com