{"answers":{"affected":"2 open source packages ship an affected version, including ewe. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34715 exists.","fix":"Upgrade ewe to 3.0.6 or later.","what":"CVE-2026-34715 is a medium-severity vulnerability in vshakitskiy ewe, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34715 and fix it if it is affected.\n\nWhat it is: CVE-2026-34715 is a medium-severity vulnerability in vshakitskiy ewe, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34715 exists.\n\nAffected packages and fixed versions:\n- ewe (Hex): affected all versions; fixed in 3.0.6\n- ewe (Hex): affected all versions; fixed in 3.0.6\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34715/ (Markdown: https://insights.sbomify.com/CVE-2026-34715/index.md)","id":"CVE-2026-34715","markdown":"https://insights.sbomify.com/CVE-2026-34715/index.md","name":"CVE-2026-34715","record":{"aliases":["GHSA-x2w3-23jr-hrpf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Gleam web server","requires_auth":"none","summary":"Attackers can inject CRLF sequences into HTTP response headers, enabling response splitting, cache poisoning, and potential XSS attacks.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ewe","vendor":"vshakitskiy"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"ewe Has Improper Neutralization of CRLF Sequences in HTTP Headers (HTTP Request/Response Splitting)","id":"CVE-2026-34715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"AVideo: DOM XSS via Unsanitized Display Name in WebSocket Call Notification","id":"CVE-2026-34716"},"packages":[{"ecosystem":"Hex","fixed":["3.0.6"],"introduced":["0"],"last_affected":[],"package":"ewe","purl":null,"source":"GHSA-x2w3-23jr-hrpf"},{"ecosystem":"Hex","fixed":["3.0.6"],"introduced":["0"],"last_affected":[],"package":"ewe","purl":"pkg:hex/ewe","source":"GHSA-x2w3-23jr-hrpf"}],"prev":{"headline":"Code injection in Vim","id":"CVE-2026-34714"},"products":["ewe"],"published":"2026-04-02","related":[{"cvss_score":7.5,"headline":"ewe: Loop with Unreachable Exit Condition ('Infinite Loop')","id":"CVE-2026-32873","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":5.3,"headline":"ewe has an Overly Permissive List of Allowed Inputs","id":"CVE-2026-32881","kev_date_added":null,"published":"2026-03-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["vshakitskiy"]},"summary":"Attackers can inject CRLF sequences into HTTP response headers, enabling response splitting, cache poisoning, and potential XSS attacks.","url":"https://insights.sbomify.com/CVE-2026-34715/"}