Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69206)
Summary
Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69206). Data can be tampered with by attackers. Exploitable via DigestAuth. Mitigation: upgrade to 0.23.35 or later.
Original description
The description as published by the source.
The DigestAuth replay defence stores lastNc + 1 rather than the nonce-count (nc) value it just accepted. When a legitimate client sends non-contiguous nc values (parallel or retried requests, as browsers do), the server's counter lags behind the highest nc seen, and a captured Authorization header can be replayed multiple times.
Impact
A passive observer can turn one captured Digest-authenticated request into several replayed authenticated (state-changing) requests, defeating the core
replay protection Digest provides over Basic.
Preconditions
- Application uses
DigestAuth. - Attacker can passively observe at least one legitimate digest request.
- Legitimate client emits an
ncmore than one greater than the last, for instance from a parallel or retried request.
Workarounds
- Deploy over TLS so requests cannot be captured.
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-69206 has been found in org.http4s:http4s-ember-core_2.12.
Attackers can target a specific entry point like DigestAuth over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade org.http4s:http4s-ember-core_2.12 to 0.23.35 or later.
If unsure, ask your IT team or search "org.http4s:http4s-ember-core_2.12 CVE-2026-69206" on the vendor's site.
CVE-2026-69206 (org.http4s:http4s-ember-core_2.12) — CWE-294 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DigestAuth / Authorization
Patched: 0.23.35 — apply immediately
Workaround: - Deploy over TLS so requests cannot be captured.
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-294) exists in org.http4s:http4s-ember-core_2.12. Attackers reach the vulnerable code path via DigestAuth without authentication.
Check the vendor advisory for the affected versions of org.http4s:http4s-ember-core_2.12. Attack surface: DigestAuth / Authorization.
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.
Update to 0.23.35.
Workaround: - Deploy over TLS so requests cannot be captured.
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-ember-core_2.12 を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
- Deploy over TLS so requests cannot be captured.パッチが適用されるまでの応急処置として、- Deploy over TLS so requests cannot be captured. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade org.http4s:http4s-ember-core_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