Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69204)
Summary
Vulnerability in org.http4s:http4s-ember-core_2.12 (CVE-2026-69204). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.23.35 or later.
Original description
The description as published by the source.
Summary
Ember's HTTP/1.1 request parser does not reject a message that carries both a
Transfer-Encoding and a Content-Length header. RFC 9112 §6.1 requires a
server to treat such a message as a framing error and close the connection.
An intermediary that follows the RFC's CL-strip-and-forward path (or that
prioritises Content-Length) will frame the body differently from Ember,
enabling HTTP request smuggling (CL.TE).
Impact
Server
Request smuggling when ember-server is an origin behind an intermediary that
forwards both headers over a keep-alive backend connection and frames by
Content-Length while Ember frames by chunked:
- Front-end security bypass: the smuggled request reaches paths the
intermediary's ACL/auth layer would have blocked, with attacker-chosen
method and headers. - Cross-user request hijack: a dangling smuggled prefix concatenates with the
next victim's request on the shared backend socket, capturing its headers. - Cache poisoning: the smuggled response is associated with the next request
key in a caching proxy.
Client
ember-client shares the same parser on the response path. An upstream that
sends both headers can desync a pooled client connection. This requires a
malicious or compromised upstream.
Preconditions
- Unauthenticated remote attacker (server)
- ember-server as origin behind a keep-alive intermediary
- Intermediary forwards a request carrying both
Transfer-Encodingand
Content-Length(RFC says it MAY…
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-69204 has been found in org.http4s:http4s-ember-core_2.12.
Risk of unauthorized operations or information disclosure.
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-69204" on the vendor's site.
CVE-2026-69204 (org.http4s:http4s-ember-core_2.12) — CWE-444
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-444) exists in org.http4s:http4s-ember-core_2.12.
Check the vendor advisory for the affected versions of org.http4s:http4s-ember-core_2.12.
Severity: ?. 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
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com