Vulnerability in org.http4s:http4s-client_2.12 (CVE-2026-69215)
Summary
Vulnerability in org.http4s:http4s-client_2.12 (CVE-2026-69215). Confidential information can be exposed externally. Exploitable via CookieJar. Mitigation: upgrade to 0.23.35 or later.
Original description
The description as published by the source.
The CookieJar client middleware decides whether to attach a cookie to an outgoing request using an unanchored substring test on the host and path, instead of the domain match specified by RFC6265 5.1.3. A cookie stored for example.com is therefore sent to any host whose name merely contains example.com (e.g. evilexample.com), leaking potentially sensitive cookies to an attacker-chosen host.
Impact
Disclosure of session and authentication cookies to an attacker-controlled host, enabling session hijack of the application's outbound calls.
Preconditions
- Application uses the
CookieJarclient middleware. - Application can be induced to make an outbound request to a host controlled by the attacker, where the hostname contains the targeted domain as a substring.
Workarounds
- Do not use the
CookieJarwith clients that fetch attacker-influenced URLs - Apply a separate
CookieJarper trusted origin.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-69215 has been found in org.http4s:http4s-client_2.12.
Attackers can target a specific entry point like CookieJar over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade org.http4s:http4s-client_2.12 to 0.23.35 or later.
If unsure, ask your IT team or search "org.http4s:http4s-client_2.12 CVE-2026-69215" on the vendor's site.
CVE-2026-69215 (org.http4s:http4s-client_2.12) — CWE-565 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CookieJar / example.com / evilexample.com
Patched: 0.23.35 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-565) exists in org.http4s:http4s-client_2.12. Attackers reach the vulnerable code path via CookieJar without authentication.
Check the vendor advisory for the affected versions of org.http4s:http4s-client_2.12. Attack surface: CookieJar / example.com / evilexample.com.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 0.23.35.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.http4s:http4s-client_2.12 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.http4s:http4s-client_2.12 to 0.23.35ステージング環境で 0.23.35 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com