CVE-2026-34715
ewe is a Gleam web server. Prior to version 3.0.6, the …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vshakitskiy/ewe/security/advisories/GHSA-x2w3-23jr-hrpf
- github.com/advisories/GHSA-x2w3-23jr-hrpf
- github.com/vshakitskiy/ewe/commit/ce4ff214d32626a10fda9398dc94a2d720e17446
- github.com/vshakitskiy/ewe/releases/tag/v3.0.6
- nvd.nist.gov/vuln/detail/CVE-2026-34715
- nvd.nist.gov/vuln/detail/CVE-2026-34715
- cve.org/CVERecord?id=CVE-2026-34715
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.