CVE-2026-69203 json
Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
published last mo. modified last mo. also EUVD-2026-79194 , GHSA-9vwc-pc8p-253q
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.http4s:http4s-ember-core_2.12 0.23.35
- maven org.http4s:http4s-ember-core_2.13 0.23.35, 1.0.0-M47
- maven org.http4s:http4s-ember-core_3 0.23.35, 1.0.0-M47
- typelevel http4s 0.23.35, 1.0.0-M47
- org.http4s http4s-ember-core_2.12 0.23.35
- org.http4s http4s-ember-core_2.13 0.23.35, 1.0.0-M47
- org.http4s http4s-ember-core_3 0.23.35, 1.0.0-M47
Is CVE-2026-69203 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.http4s:http4s-ember-core_2.12 | <0.23.35 |
0.23.35 |
| maven | org.http4s:http4s-ember-core_2.13 | <0.23.35 >=1.0.0-M1, <1.0.0-M47 |
0.23.35 1.0.0-M47 |
| maven | org.http4s:http4s-ember-core_3 | <0.23.35 >=1.0.0-M1, <1.0.0-M47 |
0.23.35 1.0.0-M47 |
Affected products
- http4s http4s
Classification
References
Sources
- CVE List CVE-2026-69203
- GitHub Advisory GHSA-9vwc-pc8p-253q
- NVD CVE-2026-69203
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.