CVE-2026-69214: Http4s: CookieJar middleware accepts arbitrary Set-Cookie domain

Published Sep 15, 2026
·
Updated

Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, The CookieJar client middleware stores a response cookie’s Domain attribute without checking that it domain-matches the host that supplied the cookie or rejecting public suffixes. A malicious or compromised server contacted through the same CookieJar can plant a cookie for another domain, and the jar later sends that cookie to the victim domain, enabling session fixation or overwriting security-sensitive cookies. The patch validates the Set-Cookie domain against the response origin, although public-suffix rejection remains unimplemented. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

Affected Software

1 affected component
http4s CookieJar middleware>0.23.35<1.0.0-M47

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade http4s to a version that resolves this vulnerability.

    Fixed in 0.23.35
  2. Upgrade

    Upgrade http4s to a version that resolves this vulnerability.

    Fixed in 1.0.0-M47

Event History

Sep 15, 2026
CVE Published
via MITRE·07:04 PM
Data Sourced
via MITRE·07:04 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are realistically exposed to this issue?

Applications using Http4s CookieJar client middleware before version 0.23.35 or 1.0.0-M47 are exposed when the same cookie jar contacts an attacker-controlled or compromised server and later makes requests to another domain.

2

What does an attacker need to exploit this?

An attacker needs to control, or compromise, a server that the affected client contacts through the shared CookieJar. That server can return a Set-Cookie header with a Domain attribute for a different target domain, causing the jar to later send the planted cookie to that domain.

3

Are fixed versions fully protected from cross-domain cookie planting?

Versions 0.23.35 and 1.0.0-M47 validate that a Set-Cookie Domain domain-matches the response origin. However, public-suffix rejection remains unimplemented.

4

What is the remediation?

Upgrade to Http4s version 0.23.35 or 1.0.0-M47. The fix prevents a response from setting a cookie domain that does not domain-match the host that supplied the response.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203