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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-113"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34715.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:vshakitskiy:ewe:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "3.0.6"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "ce4ff214d32626a10fda9398dc94a2d720e17446"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v3.0.6",
"range": [
{
"fixed": "9f26359becaf1b6c05f60571df9e22b08d7eddfe"
}
],
"source": "REFERENCES_TAG"
}
]
}