Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-69213 high CVSS 7.5

Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69213)

Summary

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

Original description

The description as published by the source.

Ember's HTTP/2 connection serializes all outgoing frames through a single unbounded queue drained by one writer fiber (writeLoop). When the write side stalls, any frames the connection keeps producing accumulate in that queue without limit. The peer can drive this cheaply because the connection emits a control frame in response to inbound frames it does not flow-control: one PING ACK per PING, one SETTINGS ACK per SETTINGS, and a WINDOW_UPDATE per inbound DATA. A single unauthenticated connection can therefore exhaust heap and OOM the process.

This affects an ember server (malicious client) and an ember client (malicious/compromised server that floods the client and stops reading its ACKs).

Impact

Unauthenticated remote denial of service (OOM) against any ember server built .withHttp2, from a single connection, at negligible attacker cost (tiny control frames). Also affects an ember client talking to a hostile HTTP/2 server.

Preconditions

  • Ember server or client built .withHttp2, speaking to a hostile or compromised peer.

Workarounds

  • Disable HTTP/2 (do not call .withHttp2).

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-69213 has been found in org.http4s:http4s-ember-core_2.12.
Attackers can target a specific entry point like writeLoop 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-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-69213" on the vendor's site.

CVE-2026-69213 (org.http4s:http4s-ember-core_2.12) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: writeLoop / PING / SETTINGS / WINDOW_UPDATE
Patched: 0.23.35 — apply immediately
Workaround: - Disable HTTP/2 (do not call .withHttp2).
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-core_2.12. Attackers reach the vulnerable code path via writeLoop without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.http4s:http4s-ember-core_2.12. Attack surface: writeLoop / PING / SETTINGS / WINDOW_UPDATE.

🔥 Severity

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

🔧 How to fix

Update to 0.23.35.

🛡️ Workaround

Workaround: - Disable HTTP/2 (do not call .withHttp2).

🔍 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-core_2.12 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    - Disable HTTP/2 (do not call `.withHttp2`).

    パッチが適用されるまでの応急処置として、- Disable HTTP/2 (do not call .withHttp2). を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.http4s:http4s-ember-core_2.12 to 0.23.35

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

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

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

Affected packages

maven org.http4s:http4s-ember-core_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.35"}]}]
maven org.http4s:http4s-ember-core_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M47"}]}]
maven org.http4s:http4s-ember-core_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