CVE-2026-69202

Http4s Ember HTTP/2: unbounded inbound body buffering

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, 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.

Analysis

AI-generated

Technical impact

A host‑driven HTTP/2 client or server can send data faster than the application consumes it, because Ember replenishes the flow‑control window based on receipt rather than consumption and stores each stream’s payload in an unheap allocation that can grow without bound, leading to severe memory exhaustion or application crashes. The weakness is reflected in CWE‑400 and CWE‑770.

Affected Systems

Versions of http4s Ember prior to 0.23.35 and 1.0.0-M47 are affected. Both the server and client components that enable HTTP/2 with withHttp2 may be vulnerable.

Risk and Exploitability

The CVSS score of 7.5 indicates high severity, and the EPSS score of <1% indicates a very low exploitation probability. This vulnerability has not been listed in CISA’s KEV catalog. An attacker can exploit this by initiating a hydra‑style upload to a target that accepts HTTP/2 traffic, causing memory pressure that may render the service unavailable.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade http4s Ember to version 0.23.35 orMploy the application so it uses the updated library dependency.
  • If HTTP/2 is not required, disable HTTP/2 in the project configuration to eliminate exploitation surface.
  • If upgrading is not immediately possible, install a reverse proxy or firewall that throttles HTTP/2 upload rates or imposes a maximum request body size to reduce memory pressure.

Generated by OpenCVE AI on September 20, 2026 at 11:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6m4x-pp6q-5jmm Http4s Ember HTTP/2: unbounded inbound body buffering
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, 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.
Title Http4s Ember HTTP/2: unbounded inbound body buffering
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:39 PM
Reserved
Aug 3, 2026, 4:57 PM
Status
Deferred
Published
Sep 15, 2026, 8:17 PM
Modified
Sep 16, 2026, 8:38 PM