Categories
CVE-2026-69208 high CVSS 7.5

Vulnerability in org.http4s:http4s-ember-server_2.12 (CVE-2026-69208)

Summary

Vulnerability in org.http4s:http4s-ember-server_2.12 (CVE-2026-69208). Risk of unauthorized operations or information disclosure. Exploitable via DigestAuth. Mitigation: upgrade to 0.23.35 or later.

Original description

The description as published by the source.

Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, the DigestAuth server middleware removes fresh nonces and stops eviction at the first stale nonce because its stale-nonce comparison is inverted. On an application that protects at least one route with DigestAuth, an unauthenticated attacker can repeatedly trigger authentication challenges, causing the persistent nonce map to grow until the JVM exhausts heap memory. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

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-69208 has been found in org.http4s:http4s-ember-server_2.12.
Attackers can target a specific entry point like DigestAuth over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade org.http4s:http4s-ember-server_2.12 to 0.23.35 or later.
If unsure, ask your IT team or search "org.http4s:http4s-ember-server_2.12 CVE-2026-69208" on the vendor's site.

CVE-2026-69208 (org.http4s:http4s-ember-server_2.12) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DigestAuth
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.

❓ What is the problem

A vulnerability (CWE-400) exists in org.http4s:http4s-ember-server_2.12. Attackers reach the vulnerable code path via DigestAuth without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.http4s:http4s-ember-server_2.12. Attack surface: DigestAuth.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.23.35.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.http4s:http4s-ember-server_2.12 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.http4s:http4s-ember-server_2.12 to 0.23.35

    ステージング環境で 0.23.35 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.http4s:http4s-ember-server_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.35"}]}]
maven org.http4s:http4s-ember-server_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M47"}]}]
maven org.http4s:http4s-ember-server_3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M47"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details