Vulnerability in org.http4s:http4s-client_2.12 (CVE-2026-69214)
Summary
Vulnerability in org.http4s:http4s-client_2.12 (CVE-2026-69214). Data can be tampered with by attackers. Exploitable via CookieJar. Mitigation: upgrade to 0.23.35 or later.
Original description
The description as published by the source.
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.
Impact
Session fixation and overwrite of security-relevant cookies for arbitrary domains contacted by the same wrapped client.
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.
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-69214 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.
Data can be tampered with by attackers. 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-69214" on the vendor's site.
CVE-2026-69214 (org.http4s:http4s-client_2.12) — CWE-384 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CookieJar / Domain
Patched: 0.23.35 — apply immediately
Workaround: - Do not share a CookieJar across trusted and untrusted targets.
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-384) 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 / Domain.
Severity: Medium (CVSS 6.8/10). Data can be tampered with by attackers.
Update to 0.23.35.
Workaround: - Do not share a CookieJar across trusted and untrusted targets.
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 temporary workaround mitigate
- Do not share a `CookieJar` across trusted and untrusted targets.パッチが適用されるまでの応急処置として、- Do not share a
CookieJaracross trusted and untrusted targets. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade org.http4s:http4s-client_2.12 to 0.23.35ステージング環境で 0.23.35 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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