Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-gq9p-f254-h286

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

CVSS 7.5 HighEPSS 0.0063 · 50th percentile

Published by the GitHub Advisory Database at 15 Sept 2026, 20:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.http4s:http4s-ember-core_2.13Maven<0.23.37 || >=1.0.0-M1, <1.0.0-M480.23.37, 1.0.0-M48
org.http4s:http4s-ember-core_2.12Maven<0.23.370.23.37
org.http4s:http4s-ember-core_3Maven<0.23.37 || >=1.0.0-M1, <1.0.0-M480.23.37, 1.0.0-M48
Identifiers
GHSA-gq9p-f254-h286 · CVE-2026-88975
Weakness (CWE)
CWE-400
Tags
Published
15 Sept 2026
Updated
15 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Http4s Ember HTTP/2 (http4s-ember-core) versions before 0.23.37, and 1.0.0-M1 up to but not including 1.0.0-M48, are affected. An unauthenticated remote peer that can open an HTTP/2 connection can make the server or client buffer up to 16 MiB of a single frame before the frame size is checked, which can lead to memory exhaustion and denial of service. Upgrade to 0.23.37 or 1.0.0-M48. Ember's HTTP/2 support is off by default, so disabling HTTP/2 or terminating it at a proxy that enforces frame size avoids exposure.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 50th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.