Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-69205 high CVSS 8.7

Vulnerability in org.http4s:http4s-ember-core_3 (CVE-2026-69205)

Summary

Vulnerability in org.http4s:http4s-ember-core_3 (CVE-2026-69205). Confidential information can be exposed externally. Exploitable via String.equalsIgnoreCase. Mitigation: upgrade to 1.0.0-M47 or later.

Original description

The description as published by the source.

Summary

Ember's HTTP/1.1 header parser matches the Transfer-Encoding header value
with a case-sensitive substring test (hValue.contains("chunked")). RFC
9112 §7 requires transfer-coding names to be compared case-insensitively. A
request carrying Transfer-Encoding: Chunked (capital C) is therefore not
recognised as chunked, and Ember falls back to framing by Content-Length
(or zero if absent) while a compliant intermediary frames the same bytes by
chunked encoding. The two parsers then disagree on where the request body
ends, enabling HTTP request smuggling (TE.CL / TE.0).

The same line of code admits two further variants:

  • The substring test misfires on Transfer-Encoding: notchunked (an inverse
    desync — Ember treats it as chunked while a compliant intermediary
    rejects the unknown coding).
  • Header field bytes are decoded with the platform-default charset. Under
    UTF-8 the wire bytes E2 84 AA decode to U+212A KELVIN SIGN, which
    String.equalsIgnoreCase Unicode-case-folds to k, so
    Transfer-Encoding: chuned matches chunked once the comparison
    is made case-insensitive without also pinning the decode to ISO-8859-1.

Impact

Server

Request smuggling when ember-server is an origin behind an intermediary that
honours Transfer-Encoding case-insensitively per RFC, forwards the header
value verbatim, and reuses keep-alive connections to the backend:

  • Front-end security bypass: the smuggled request reaches paths the
    intermediary's ACL/au…

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-69205 has been found in org.http4s:http4s-ember-core_3.
Attackers can target a specific entry point like String.equalsIgnoreCase over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade org.http4s:http4s-ember-core_3 to 1.0.0-M47 or later.
If unsure, ask your IT team or search "org.http4s:http4s-ember-core_3 CVE-2026-69205" on the vendor's site.

CVE-2026-69205 (org.http4s:http4s-ember-core_3) — CWE-444 / CVSS v3 8.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: String.equalsIgnoreCase / chunked / Cookie / Authorization
Patched: 1.0.0-M47 — 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-444) exists in org.http4s:http4s-ember-core_3. Attackers reach the vulnerable code path via String.equalsIgnoreCase without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.http4s:http4s-ember-core_3. Attack surface: String.equalsIgnoreCase / chunked / Cookie / Authorization.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.0.0-M47.

🛡️ 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-core_3 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.http4s:http4s-ember-core_3 to 1.0.0-M47

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

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

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

Affected packages

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

References

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