Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cp4q-fqw9-4hf6 | Http4s Ember HTTP/2: unbounded continuation frame accumulation |
Tue, 15 Sep 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Http4s
Http4s http4s |
|
| Vendors & Products |
Http4s
Http4s http4s |
Tue, 15 Sep 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, When Ember receives an HTTP/2 HEADERS or PUSH_PROMISE frame without END_HEADERS, H2Connection buffers the header block and subsequent CONTINUATION fragments without a size bound. A remote peer can keep an incomplete block open and exhaust heap memory before request decoding, affecting an ember-server or ember-client configured with withHttp2. The remediation tracks accumulated size against SETTINGS_MAX_HEADER_LIST_SIZE derived from EmberServerBuilder.maxHeaderSize or EmberClientBuilder.maxResponseHeaderSize, sends GOAWAY when the limit is exceeded, and applies receiveHeadersTimeout to incomplete blocks. This issue is fixed in versions 0.23.35 and 1.0.0-M47. | |
| Title | Http4s Ember HTTP/2: unbounded continuation frame accumulation | |
| Weaknesses | CWE-770 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-15T19:22:57.407Z
Reserved: 2026-08-03T16:57:50.125Z
Link: CVE-2026-69218
No data.
Status : Received
Published: 2026-09-15T20:17:41.310
Modified: 2026-09-15T20:17:41.310
Link: CVE-2026-69218
No data.
OpenCVE Enrichment
Updated: 2026-09-15T21:30:15Z
-
CWE-770
Allocation of Resources Without Limits or Throttling
Github GHSA