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.
CVE-2026-69203
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026v1.0.0-M47
Patch available: http4s/http4s v1.0.0-M47 (pre-release)
https://github.com/http4s/http4s/releases/tag/v1.0.0-M47v0.23.35
Patch available: http4s/http4s v0.23.35
https://github.com/http4s/http4s/releases/tag/v0.23.35commit 4983de1f93f2 (http4s/http4s)
Patch available: http4s/http4s v0.23.35 (contains commit 4983de1f93f2)
https://github.com/http4s/http4s/commit/4983de1f93f2caaa3b9de310cf6a9db32c50d66eEmber HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS · Advisory · http4s/http4s · GitHub
https://github.com/http4s/http4s/security/advisories/GHSA-9vwc-pc8p-253qVendor Advisories for CVE-2026-69203(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
Maven(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.http4s:http4s-ember-core_2.12 | 0.10.0-M10 ... 0.23.9 (114 versions) | 0.23.35 | — |
| org.http4s:http4s-ember-core_2.13 | 0.10.0-M10 ... 0.23.9 (114 versions) | 0.23.35 | — |
| org.http4s:http4s-ember-core_3 | 0.22.0 ... 0.23.9 (58 versions) | 0.23.35 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 06:06 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:54 UTCEG score recompute
- 2026-09-16 20:11 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:40 UTCEG score recompute
- 2026-09-15 19:43 UTCEG score recompute
- 2026-09-15 19:23 UTCEG score recompute
- 2026-09-15 19:22 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-69203?
When was CVE-2026-69203 disclosed?
Is CVE-2026-69203 actively exploited?
What is the CVSS score of CVE-2026-69203?
How do I remediate CVE-2026-69203?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69203
Is Your Infrastructure Affected by CVE-2026-69203?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.