CVE-2026-88975
- Source
- https://cve.org/CVERecord?id=CVE-2026-88975
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-88975.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-88975
- Aliases
- Published
- 2026-09-15T19:31:25Z
- Modified
- 2026-09-18T03:31:01Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-400" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88975.json" }- References
-
- https://github.com/http4s/http4s/releases/tag/v0.23.37
- https://github.com/http4s/http4s/releases/tag/v1.0.0-M48
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/88xxx/CVE-2026-88975.json
- https://github.com/http4s/http4s/security/advisories/GHSA-gq9p-f254-h286
- https://nvd.nist.gov/vuln/detail/CVE-2026-88975
- https://github.com/http4s/http4s/commit/87cf334fa3f608ef7d3eb359e71e037ba3336d29
Affected packages
Git / github.com/http4s/http4s
Affected ranges
- Type
- GIT
- Repo
- https://github.com/http4s/http4s
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedIntroducedFixedFixedFixed
- Database specific
-
Show details
{ "extracted_events": [ { "introduced": "0" }, { "fixed": "0.23.37" }, { "introduced": "1.0.0-M1" }, { "fixed": "1.0.0-M48" } ], "source": [ "AFFECTED_FIELD", "REFERENCES" ] }
Affected versions
v0.*
v0.23.0
v0.23.0-M1
v0.23.1
v0.23.10
v0.23.11
v0.23.12
v0.23.13
v0.23.14
v0.23.15
v0.23.16
v0.23.18
v0.23.19
v0.23.19-RC1
v0.23.19-RC2
v0.23.2
v0.23.20
v0.23.22
v0.23.23
v0.23.24
v0.23.25
v0.23.26
v0.23.27
v0.23.28
v0.23.29
v0.23.3
v0.23.30
v0.23.31
v0.23.32
v0.23.33
v0.23.34
v0.23.36
v0.23.5
v0.23.6
v0.23.7
v0.23.8
v0.23.9
v1.*
v1.0.0-M1
v1.0.0-M10
v1.0.0-M11
v1.0.0-M12
v1.0.0-M13
v1.0.0-M15
v1.0.0-M16
v1.0.0-M17
v1.0.0-M19
v1.0.0-M2
v1.0.0-M20
v1.0.0-M21
v1.0.0-M22
v1.0.0-M24
v1.0.0-M26
v1.0.0-M28
v1.0.0-M29
v1.0.0-M3
v1.0.0-M30
v1.0.0-M31
v1.0.0-M32
v1.0.0-M33
v1.0.0-M34
v1.0.0-M35
v1.0.0-M36
v1.0.0-M37
v1.0.0-M39
v1.0.0-M4
v1.0.0-M40
v1.0.0-M41
v1.0.0-M42
v1.0.0-M43
v1.0.0-M44
v1.0.0-M45
v1.0.0-M46
v1.0.0-M5
v1.0.0-M6
v1.0.0-M7
v1.0.0-M8
v1.0.0-M9