CVE-2026-69203

published 15 Sep 2026 · updated 15 Sep 2026

Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, An Ember server with HTTP/2 enabled through withHttp2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS for peer-created streams. One unauthenticated connection can open an unbounded number of streams, each retaining per-stream state until heap exhaustion. The same unchecked allocation is reachable in an ember-client through server-initiated PUSH_PROMISE frames because enablePush is not enforced. This issue is fixed in versions 0.23.35 and 1.0.0-M47.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
http4s<0.23.35, >=1.0.0-M1 <1.0.0-M47

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-69203 severity on Zeptric[![CVE-2026-69203](https://zeptric.io/badge/cve/CVE-2026-69203.svg)](https://zeptric.io/cve/CVE-2026-69203)