CVE-2026-88975

Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE

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.37 and 1.0.0-M48, Ember’s HTTP/2 read loop parses a frame’s 24-bit declared length but waits to buffer the entire payload before comparing it with SETTINGS_MAX_FRAME_SIZE. An unauthenticated peer can declare a payload near 16 MiB on a connection where Ember advertised 16 KiB and either complete or slowly stream it, causing up to 1024-fold memory amplification per connection before processFrame can reject the frame. The shared H2Connection.readLoop affects withHttp2 servers and clients, while HTTP/2-disabled configurations are unaffected, and the patch rejects oversized frames before buffering their payloads. This issue is fixed in versions 0.23.37 and 1.0.0-M48.

Analysis

AI-generated

Technical impact

Http4s’s Ember HTTP/2 implementation parses a frame’s declared 24-bit length but delays buffering the payload until after it compares that length with SETTINGS_MAX_FRAME_SIZE. An unauthenticated peer can declare a payload almost 16 MiB on a connection that has advertised a maximum of 16 KiB. Because the payload is buffered before the size check, the process can consume up to 1024‑fold more memory than intended, leading to a denial‑of‑service condition. This flaw is an instance of uncontrolled resource consumption (CWE-400).

Affected Systems

The vulnerability affects any project that incorporates the http4s library and uses Ember’s shared HTTP/2 read loop, whether as a server or client. Versions prior to 0.23.37 and 1.0.0-M48 are vulnerable, while HTTP/2-disabled configurations are unaffected.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity issue. The EPSS score of <1% indicates a very low but nonzero exploitation probability. The CVE description explicitly states that an unauthenticated peer can declare a payload near 16 MiB on a connection where Ember advertised 16 KiB, causing memory amplification before the frame is rejected. This implies that an attacker who can initiate an HTTP/2 connection could exploit this flaw; this inference is based on the description. The vulnerability is not listed in the CISA KEV catalog. The patch introduced in versions 0.23.37 and 1.0.0-M48 rejects oversized frames before buffering their payloads, eliminating the amplification vector.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade http4s to version 0.23.37 or newer, or 1.0.0-M48 or newer, ensuring that the Ember HTTP/2 read loop applies the mitigated logic.
  • If an upgrade cannot be performed immediately, either disable HTTP/2 on the affected services or enforce a stricter maximum frame size before the application is patched to prevent large payloads from being accepted.
  • Monitor process memory usage and configure alerting for abnormal spikes exploitation can be detected and mitigated before a full denial of service occurs.

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

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gq9p-f254-h286 Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Http4s
Http4s http4s
Vendors & Products Http4s
Http4s http4s
Type Values Removed Values Added
Description Http4s is a Scala interface for HTTP services. Prior to 0.23.37 and 1.0.0-M48, Ember’s HTTP/2 read loop parses a frame’s 24-bit declared length but waits to buffer the entire payload before comparing it with SETTINGS_MAX_FRAME_SIZE. An unauthenticated peer can declare a payload near 16 MiB on a connection where Ember advertised 16 KiB and either complete or slowly stream it, causing up to 1024-fold memory amplification per connection before processFrame can reject the frame. The shared H2Connection.readLoop affects withHttp2 servers and clients, while HTTP/2-disabled configurations are unaffected, and the patch rejects oversized frames before buffering their payloads. This issue is fixed in versions 0.23.37 and 1.0.0-M48.
Title Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE
Weaknesses CWE-400
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

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 16, 2026, 2:43 PM
Reserved
Sep 10, 2026, 4:02 PM
Status
Deferred
Published
Sep 15, 2026, 8:19 PM
Modified
Sep 16, 2026, 8:39 PM