{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-69211 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-69211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-69211 is a medium-severity vulnerability in http4s, published on 15 Sep 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-69211 and fix it if it is affected.\n\nWhat it is: CVE-2026-69211 is a medium-severity vulnerability in http4s, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-69211 in the wild and no public exploit code.\n\nAffected product: http4s. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-69211/ (Markdown: https://insights.sbomify.com/CVE-2026-69211/index.md)","id":"CVE-2026-69211","markdown":"https://insights.sbomify.com/CVE-2026-69211/index.md","name":"CVE-2026-69211","record":{"aliases":["GHSA-7qh7-rghh-698h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Scala HTTP library","requires_auth":"none","summary":"Attackers can inject cookie attributes or split headers via unvalidated input in Http4s, weakening cookie security and potentially enabling header injection.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1286","name":"Improper Validation of Syntactic Correctness of Input"},{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, ResponseCookie.render writes attacker-influenced name, content, domain, path, and extension values without neutralizing semicolons or control characters. An application that constructs a ResponseCookie from unvalidated input can therefore emit injected cookie attributes such as Domain, Path, or SameSite, widening cookie scope or weakening protections, and control characters may enable header splitting on permissive backends. The patch strips control characters from all five fields and strips semicolons from name, content, domain, and path while retaining the extension delimiter behavior. This issue is fixed in versions 0.23.35 and 1.0.0-M47.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Http4s: Set-Cookie rendering does not escape attribute delimiters","id":"CVE-2026-69211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Http4s: FollowRedirect middleware leaks credentials over https-\u003ehttp same-authority redirect","id":"CVE-2026-69212"},"packages":[],"prev":{"headline":"Http4s: WebSocket decoder accepts negative length, causing infinite decode loop","id":"CVE-2026-69210"},"products":["http4s"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["http4s"]},"summary":"Attackers can inject cookie attributes or split headers via unvalidated input in Http4s, weakening cookie security and potentially enabling header injection.","url":"https://insights.sbomify.com/CVE-2026-69211/"}