CVE-2026-69215: Http4s: CookieJar middleware matches by substring, leaking cookies cross-origin

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 uses unanchored substring checks instead of RFC 6265 domain and path matching when deciding whether to attach a stored cookie. A cookie for example.com can consequently be sent to an attacker-controlled hostname such as evilexample.com when an application using the same jar makes an attacker-influenced outbound request. This exposes session or authentication cookies and can enable hijacking of the application’s outbound sessions. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

Affected Software

2 affected components
Http4s Http4s<0.23.35, >0.23.35<=1.0.0-M47
Http4s Http4s<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:17 PM
Data Sourced
via MITRE·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are realistically exposed?

Applications using Http4s CookieJar client middleware are exposed when they reuse a cookie jar containing cookies for a legitimate domain and make outbound requests to attacker-influenced hostnames. A hostname such as evilexample.com can receive a cookie intended for example.com.

2

What does an attacker need to exploit this issue?

An attacker needs to influence an outbound request made by the application using the same CookieJar. No attacker authentication or user interaction is required, but the attack depends on the application making a request to a hostname that triggers the substring match.

3

What should be done if patching is not immediately possible?

Avoid making attacker-influenced outbound requests with a CookieJar that contains session or authentication cookies. Separating cookie jars by trust boundary can reduce the chance that cookies for legitimate services are attached to untrusted destinations.

4

How can I determine whether my deployment is affected?

Check whether the application uses Http4s CookieJar client middleware and is running a version earlier than 0.23.35 or 1.0.0-M47. Also identify flows where a shared jar sends requests to attacker-controlled or otherwise untrusted hostnames.

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