Summary
Http4s: CookieJar middleware accepts arbitrary Set-Cookie domain
When processing a Set-Cookie from a response, the CookieJar client middleware trusts the server-supplied Domain attribute verbatim, with no check that it domain-matches the host that sent the cookie (RFC6265 §5.3 step 6) and no public suffix check. A malicious or compromised server can therefore plant a cookie for any domain in the cookie jar, which is subsequently set on the client's next request to that victim domain, enabling session fixation or overwriting security-relevant cookies.
Preconditions
- Application uses the
CookieJarclient middleware. - Application contacts an attacker-controlled (or compromised) server using the same jar it uses for trusted hosts.
Workarounds
- Do not share a
CookieJaracross trusted and untrusted targets.
Note
This middleware still does not implement public suffix rejection.
Impact
Session fixation and overwrite of security-relevant cookies for arbitrary domains contacted by the same wrapped client.
CVE-2026-69214 has a CVSS score of 6.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.23.35, 1.0.0-M47); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.http4s:http4s-client_2.12 to 0.23.35 or later; org.http4s:http4s-client_2.13 to 0.23.35 or later; org.http4s:http4s-client_2.13 to 1.0.0-M47 or later; org.http4s:http4s-client_3 to 1.0.0-M47 or later; org.http4s:http4s-client_3 to 0.23.35 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-69214? CVE-2026-69214 is a medium-severity security vulnerability in org.http4s:http4s-client_2.12 (maven), affecting versions <= 0.23.34. It is fixed in 0.23.35, 1.0.0-M47.
- How severe is CVE-2026-69214? CVE-2026-69214 has a CVSS score of 6.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-69214?
org.http4s:http4s-client_2.12(maven) (versions <= 0.23.34)org.http4s:http4s-client_2.13(maven) (versions <= 0.23.34)org.http4s:http4s-client_3(maven) (versions >= 1.0.0-M1, <= 1.0.0-M46)
- Is there a fix for CVE-2026-69214? Yes. CVE-2026-69214 is fixed in 0.23.35, 1.0.0-M47. Upgrade to this version or later.
- Is CVE-2026-69214 exploitable, and should I be worried? Whether CVE-2026-69214 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-69214 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-69214?
- Upgrade
org.http4s:http4s-client_2.12to 0.23.35 or later - Upgrade
org.http4s:http4s-client_2.13to 0.23.35 or later - Upgrade
org.http4s:http4s-client_2.13to 1.0.0-M47 or later - Upgrade
org.http4s:http4s-client_3to 1.0.0-M47 or later - Upgrade
org.http4s:http4s-client_3to 0.23.35 or later
- Upgrade