Answer in brief
CVE-2026-69202 records a High severity (CVSS 7.5) vulnerability in Http4s Ember HTTP/2: unbounded inbound body buffering. The current sources do not mark it as known exploited. The current feed maps http4s/http4s (generic), org.http4s:http4s-ember-core_2.12 (maven), org.http4s:http4s-ember-core_2.13 (maven), org.http4s:http4s-ember-core_2.13 (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps http4s/http4s (generic), org.http4s:http4s-ember-core_2.12 (maven), org.http4s:http4s-ember-core_2.13 (maven), org.http4s:http4s-ember-core_2.13 (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| http4s/http4sgeneric | < 0.23.35 || >= 1.0.0-M1, < 1.0.0-M47 | Not reported |
| org.http4s:http4s-ember-core_2.12maven | <=0.23.34 | 0.23.35 |
| org.http4s:http4s-ember-core_2.13maven | <=0.23.34 | 0.23.35 |
| org.http4s:http4s-ember-core_2.13maven | >=1.0.0-M1,<=1.0.0-M46 | 1.0.0-M47 |
| org.http4s:http4s-ember-core_3maven | <=0.23.34 | 0.23.35 |
| org.http4s:http4s-ember-core_3maven | >=1.0.0-M1,<=1.0.0-M46 | 1.0.0-M47 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 15, 2026
Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, Ember’s HTTP/2 flow-control window is replenished according to bytes received from the network rather than bytes consumed by the application, while each stream stores DATA in an unbounded channel. A hostile peer can therefore send a body faster than a slow or non-draining application consumes it, retaining payloads in heap on an ember-server or ember-client configured with withHttp2. The patch bounds the per-stream H2Connection body channel so application consumption applies backpressure. This issue is fixed in versions 0.23.35 and 1.0.0-M47.
Quoted source text, attributed separately from HOL analysis.