Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69218)
Summary
Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69218). Risk of unauthorized operations or information disclosure. Exploitable via HEADERS. 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, When Ember receives an HTTP/2 HEADERS or PUSH_PROMISE frame without END_HEADERS, H2Connection buffers the header block and subsequent CONTINUATION fragments without a size bound. A remote peer can keep an incomplete block open and exhaust heap memory before request decoding, affecting an ember-server or ember-client configured with withHttp2. The remediation tracks accumulated size against SETTINGS_MAX_HEADER_LIST_SIZE derived from EmberServerBuilder.maxHeaderSize or EmberClientBuilder.maxResponseHeaderSize, sends GOAWAY when the limit is exceeded, and applies receiveHeadersTimeout to incomplete blocks. 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-69218 has been found in org.http4s:http4s-ember-core_2.12.
Attackers can target a specific entry point like HEADERS 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-69218" on the vendor's site.
CVE-2026-69218 (org.http4s:http4s-ember-core_2.12) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: HEADERS / PUSH_PROMISE / END_HEADERS / CONTINUATION
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-770) exists in org.http4s:http4s-ember-core_2.12. Attackers reach the vulnerable code path via HEADERS without authentication.
Check the vendor advisory for the affected versions of org.http4s:http4s-ember-core_2.12. Attack surface: HEADERS / PUSH_PROMISE / END_HEADERS / CONTINUATION.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
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-ember-core_2.12 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.http4s:http4s-ember-core_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
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com