Http4s up to 0.23.34/1.0.0-M46 Ember HTTP/2 Flow Control resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.90 |
Summary
A vulnerability, which was classified as problematic, has been found in Http4s up to 0.23.34/1.0.0-M46. Affected by this vulnerability is an unknown functionality of the component Ember HTTP2 Flow Control. The manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2026-69202. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Http4s up to 0.23.34/1.0.0-M46. It has been rated as problematic. This issue affects an unknown functionality of the component Ember HTTP2 Flow Control. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-69202 since 08/03/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 0.23.35 or 1.0.0-M47 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.23.0
- 0.23.1
- 0.23.2
- 0.23.3
- 0.23.4
- 0.23.5
- 0.23.6
- 0.23.7
- 0.23.8
- 0.23.9
- 0.23.10
- 0.23.11
- 0.23.12
- 0.23.13
- 0.23.14
- 0.23.15
- 0.23.16
- 0.23.17
- 0.23.18
- 0.23.19
- 0.23.20
- 0.23.21
- 0.23.22
- 0.23.23
- 0.23.24
- 0.23.25
- 0.23.26
- 0.23.27
- 0.23.28
- 0.23.29
- 0.23.30
- 0.23.31
- 0.23.32
- 0.23.33
- 0.23.34
- 1.0.0-M46
Website
- Product: https://github.com/http4s/http4s/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Http4s 0.23.35/1.0.0-M47
Timeline
08/03/2026 CVE reserved09/15/2026 Advisory disclosed
09/15/2026 VulDB entry created
09/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-69202 (🔒)
GCVE (CVE): GCVE-0-2026-69202
GCVE (VulDB): GCVE-100-404657
Entry
Created: 09/15/2026 22:03Changes: 09/15/2026 22:03 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.