CVE-2026-69203

Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS

Published Sep 15, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

An Ember HTTP/2 server that does not enforce the SETTINGS_MAX_CONCURRENT_STREAMS frame allows an unauthenticated peer to open an unbounded number of streams. Each stream consumes per-stream state; if many streams are opened, the JVM heap can be exhausted. The same unchecked allocation is also reachable in an Ember client via server-initiated PUSH_PROMISE frames when push is not enabled. The result is a denial of service that can crash or degrade the affected application.

Affected Systems

The vulnerability affects the http4s Ember HTTP/2 stack. Any deployment of Http4s Ember server or client running a version earlier than 0.23.35 or 1.0.0-M47 is susceptible.

Risk and Exploitability

The CVSS score of 7.5 indicates a moderate-to-high severity. The EPSS score is about 0.5%, indicating a very low exploitation probability. The vulnerability is not listed in CISA’s KEV catalog. An attacker can exploit the flaw over an unauthenticated HTTP/2 connection, creating multiple simultaneous streams to exhaust memory. The presence of the flaw in both server and client amplifies the attack surface, making remediation via patching the single most effective measure.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Http4s v0.23.35 or later or 1.0.0-M47 or later.
  • If upgrading is not immediately feasible, disable HTTP/2 support on servers or clients that do not require it or apply custom configuration to limit concurrent streams if the framework allows.
  • Monitor application memory usage and consider adding process hardening such as cgroups or JVM options to limit heap usage.

Generated by OpenCVE AI on September 20, 2026 at 12:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9vwc-pc8p-253q Http4s Ember HTTP/2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
History
Type Values Removed Values Added
First Time appeared Http4s
Http4s http4s
Vendors & Products Http4s
Http4s http4s
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 15, 2026, 7:36 PM
Reserved
Aug 3, 2026, 4:57 PM
Status
Deferred
Published
Sep 15, 2026, 8:17 PM
Modified
Sep 16, 2026, 8:38 PM