CVE-2026-69218: Http4s Ember HTTP/2 Unbounded Continuation Frame Accumulation Vulnerability

HIGH
Advisory Identifier: GHSA-cp4q-fqw9-4hf6
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2026-69218 is a HIGH (CVSS 7.5) unbounded continuation frame accumulation vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Http4s Ember HTTP/2 libraries in the Maven ecosystem. The issue involves unbounded continuation frame accumulation. Remediation is available by upgrading affected packages to version 0.23.35, 1.0.0-M47.

CVE-2026-69218 at a Glance

CVE Identifier CVE-2026-69218
GHSA Identifier GHSA-cp4q-fqw9-4hf6
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Http4s Ember HTTP/2
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-69218

To remediate this vulnerability, upgrade all affected Http4s Ember HTTP/2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.http4s:http4s-ember-core_2.12 fixed: 0.23.35
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.12</artifactId>
    <version>0.23.35</version>
</dependency>
org.http4s:http4s-ember-core_2.13 fixed: 0.23.35
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.13</artifactId>
    <version>0.23.35</version>
</dependency>
org.http4s:http4s-ember-core_3 fixed: 0.23.35
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_3</artifactId>
    <version>0.23.35</version>
</dependency>
org.http4s:http4s-ember-core_2.13 fixed: 1.0.0-M47
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.13</artifactId>
    <version>1.0.0-M47</version>
</dependency>
org.http4s:http4s-ember-core_3 fixed: 1.0.0-M47
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_3</artifactId>
    <version>1.0.0-M47</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.http4s

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-69218, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.http4s

Analyze the terminal output to locate any version of Http4s Ember HTTP/2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.35), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.http4s command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Http4s Ember HTTP/2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

When Ember receives an HTTP/2 `HEADERS` or `PUSH_PROMISE` frame without the `END_HEADERS` flag, it buffers the header block fragment and waits for subsequent `CONTINUATION` frames. These accumulate unbounded until the connection closes. ### Impact A remote, unauthenticated peer can exhaust the heap on any Ember endpoint that has HTTP/2 enabled: - **ember-server with `.withHttp2`**: any HTTP/2 client can trigger this against any reachable path (including paths that return 404). No authentication is required because the attack completes before the request is decoded. - **ember-client with `.withHttp2`**: a malicious or compromised origin server can trigger this via the response header block. A single in-flight request is sufficient. Memory consumption is bounded only by the attacker's upload bandwidth and the connection lifetime. ### Prerequisites - `EmberServerBuilder` configured with `.withHttp2`. - For the server: the attacker can establish an HTTP/2 connection - For the client: the application makes a request to an attacker-controlled origin. HTTP/2 incoming headers exceeding the configured size limit are buffer in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion. ### Patches The fix bounds the accumulated header-block size at `SETTINGS_MAX_HEADER_LIST_SIZE` (derived from `EmberServerBuilder.maxHeaderSize` / `EmberClientBuilder.maxResponseHeaderSize`). When a `CONTINUATION` frame would push the accumulated block over that limit, the connection is terminated with `GOAWAY`. The `receiveHeadersTimeout` additionally bounds how long an incomplete header block may remain open. ### Workarounds - Disable HTTP/2 (`.withHttp2`) until upgraded (default). It is off by default. - If HTTP/2 must remain enabled, place ember behind a reverse proxy that terminates HTTP/2 and speaks HTTP/1.1 to ember.

CVE-2026-69218 Affected Http4s Ember HTTP/2 Versions

5 component(s)
Fixed Versions:
0.23.351.0.0-M47
Product / Package Ecosystem Affected Versions Fixed Version
org.http4s:http4s-ember-core_2.12
Maven
< 0.23.35
0.23.35
org.http4s:http4s-ember-core_2.13
Maven
< 0.23.35
0.23.35
org.http4s:http4s-ember-core_3
Maven
< 0.23.35
0.23.35
org.http4s:http4s-ember-core_2.13
Maven
≥ 1.0.0-M1
< 1.0.0-M47
1.0.0-M47
org.http4s:http4s-ember-core_3
Maven
≥ 1.0.0-M1
< 1.0.0-M47
1.0.0-M47

References

Frequently Asked Questions

What is CVE-2026-69218?
CVE-2026-69218 is a security vulnerability in Http4s Ember HTTP/2 involving unbounded continuation frame accumulation under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Http4s Ember HTTP/2 versions are affected?
Affected versions include releases prior to 0.23.35, 1.0.0-M47 across affected packages: org.http4s:http4s-ember-core_2.12, org.http4s:http4s-ember-core_2.13, org.http4s:http4s-ember-core_3.
What version fixes CVE-2026-69218?
Upgrading to 0.23.35, 1.0.0-M47 (or the latest patched release for your respective branch) resolves the vulnerability.
Is http4s-ember-core_2.12 affected?
Yes, org.http4s:http4s-ember-core_2.12 is affected in releases prior to 0.23.35. Upgrade your dependency to 0.23.35 or later.
Is http4s-ember-core_2.13 affected?
Yes, org.http4s:http4s-ember-core_2.13 is affected in releases prior to 0.23.35, 1.0.0-M47. Upgrade your dependency to 0.23.35, 1.0.0-M47 or later.
What is the CVSS score of CVE-2026-69218?
CVE-2026-69218 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-69218?
CVE-2026-69218 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Maven dependencies for CVE-2026-69218?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.http4s'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cp4q-fqw9-4hf6",
  "modified" : "2026-09-15T20:01:08Z",
  "published" : "2026-09-15T20:01:08Z",
  "aliases" : [ "CVE-2026-69218" ],
  "summary" : "Http4s Ember HTTP/2: unbounded continuation frame accumulation",
  "details" : "When Ember receives an HTTP/2 `HEADERS` or `PUSH_PROMISE` frame without the `END_HEADERS` flag, it buffers the header block fragment and waits for subsequent `CONTINUATION` frames.  These accumulate unbounded until the connection closes. \n\n### Impact\n\nA remote, unauthenticated peer can exhaust the heap on any Ember endpoint that has HTTP/2 enabled:\n\n- **ember-server with `.withHttp2`**: any HTTP/2 client can trigger this against any reachable path (including paths that return 404).  No authentication is required because the attack completes before the request is decoded.\n- **ember-client with `.withHttp2`**:  a malicious or compromised origin server can trigger this via the response header block.  A single in-flight request is sufficient.\n\nMemory consumption is bounded only by the attacker's upload bandwidth and the connection lifetime.\n\n### Prerequisites\n\n- `EmberServerBuilder` configured with `.withHttp2`.\n    - For the server: the attacker can establish an HTTP/2 connection\n    - For the client: the application makes a request to an attacker-controlled origin.\nHTTP/2 incoming headers exceeding the configured size limit are buffer in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.\n\n### Patches\n\nThe fix bounds the accumulated header-block size at `SETTINGS_MAX_HEADER_LIST_SIZE` (derived from `EmberServerBuilder.maxHeaderSize` / `EmberClientBuilder.maxResponseHeaderSize`).  When a `CONTINUATION` frame would push the accumulated block over that limit, the connection is terminated with `GOAWAY`.  The `receiveHeadersTimeout` additionally bounds how long an incomplete header block may remain open.\n\n### Workarounds\n\n- Disable HTTP/2 (`.withHttp2`) until upgraded (default).  It is off by default.\n- If HTTP/2 must remain enabled, place ember behind a reverse proxy that terminates HTTP/2 and speaks HTTP/1.1 to ember.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_2.12"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.35"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.34"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_2.13"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.35"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.34"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.35"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.34"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_2.13"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0-M1"
      }, {
        "fixed" : "1.0.0-M47"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.0-M46"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0-M1"
      }, {
        "fixed" : "1.0.0-M47"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.0-M46"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/security/advisories/GHSA-cp4q-fqw9-4hf6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/commit/6e8eccd64a6a74ab4811897881e95e0e1b3a818e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/http4s/http4s"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/releases/tag/v0.23.35"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/releases/tag/v1.0.0-M47"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-15T20:01:08Z",
    "nvd_published_at" : null
  }
}