Vulnerabilities in pkg:maven/org.http4s/http4s-ember-core_2.12

PACKAGE
Advisory Identifier: GHSA-gq9p-f254-h286
Advisory Summary

CVE-2026-88975 is a HIGH (CVSS 7.5) ember http/2 buffers a frame's vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Http4s libraries in the Maven ecosystem. The issue involves ember http/2 buffers a frame's declared payload before checking settings_max_frame_size. Remediation is available by upgrading affected packages to version 0.23.37, 1.0.0-M48.

11 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.http4s/http4s-ember-core_2.12

11 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.http4s/http4s-ember-core_2.12. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-gq9p-f254-h286 CVE-2026-88975 HIGH Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE
GHSA-cp4q-fqw9-4hf6 CVE-2026-69218 HIGH Http4s Ember HTTP/2: unbounded continuation frame accumulation
GHSA-jrpm-956j-96jg CVE-2026-69216 MODERATE Http4s: Ember chunk parser lenience (TE.TE request smuggling)
GHSA-8f3q-3jmv-7prw CVE-2026-69213 HIGH Http4s Ember HTTP/2 has an unbounded outbound frame queue
GHSA-9xww-74xv-gjfp CVE-2026-69206 MODERATE Http4s: DigestAuth allows replay of captured requests
GHSA-9998-894r-fwvr CVE-2026-69205 HIGH Http4s Ember Transfer-Encoding value parsing (TE.CL / TE.0 request smuggling)
GHSA-8h4c-x2wg-6xp8 CVE-2026-69204 CRITICAL Http4s Ember accepts Transfer-Encoding combined with Content-Length (CL.TE request smuggling)
GHSA-9vwc-pc8p-253q CVE-2026-69203 HIGH Http4s Ember HTTP/2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS
GHSA-6m4x-pp6q-5jmm CVE-2026-69202 HIGH Http4s Ember HTTP/2: unbounded inbound body buffering
GHSA-vmm3-xgcx-67hm CVE-2026-54556 HIGH http4s has HTTP/2 Denial of Service with Ember Backend
GHSA-wcwh-7gfw-5wrr CVE-2025-59822 MODERATE Http4s vulnerable to HTTP Request Smuggling due to improper handling of HTTP trailer section

CVE-2026-88975 at a Glance

CVE Identifier CVE-2026-88975
GHSA Identifier GHSA-gq9p-f254-h286
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Http4s
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-88975

To remediate this vulnerability, upgrade all affected Http4s 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.13 fixed: 0.23.37
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.13</artifactId>
    <version>0.23.37</version>
</dependency>
org.http4s:http4s-ember-core_2.12 fixed: 0.23.37
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.12</artifactId>
    <version>0.23.37</version>
</dependency>
org.http4s:http4s-ember-core_3 fixed: 0.23.37
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_3</artifactId>
    <version>0.23.37</version>
</dependency>
org.http4s:http4s-ember-core_2.13 fixed: 1.0.0-M48
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_2.13</artifactId>
    <version>1.0.0-M48</version>
</dependency>
org.http4s:http4s-ember-core_3 fixed: 1.0.0-M48
<dependency>
    <groupId>org.http4s</groupId>
    <artifactId>http4s-ember-core_3</artifactId>
    <version>1.0.0-M48</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-88975, 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 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.37), 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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Http4s, 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

### Summary An unauthenticated peer can make Ember's HTTP/2 read loop hold 16 MiB of a single frame in memory on a connection where Ember advertised a 16 KiB limit. The declared length is readable from the frame's first 9 bytes, but it is not compared against SETTINGS_MAX_FRAME_SIZE until the whole payload has been read into a contiguous buffer. That is 1024x amplification per connection, bounded by the protocol's 24-bit length field rather than by any setting, and at the default maxConnections of 1024 it puts about 16 GiB of heap in reach. ### Details H2Frame.RawFrame.fromByteVector (ember-core/.../h2/H2Frame.scala:66-69) reads the length, then refuses to produce a frame until 9 + length bytes are present: ``` val length = (bv(2) & 0xff) | ((bv(1) & 0xff) << 8) | ((bv(0) & 0xff) << 16) if (bv.length >= 9 + length) { ``` readNextFrame in H2Connection.readLoop (H2Connection.scala:246-266) reads that None as "need more" and concatenates further socket reads into one accumulator until it is satisfied. The only check of an inbound frame against the connection's own SETTINGS_MAX_FRAME_SIZE is in processFrame at H2Connection.scala:534, which cannot run until the frame is assembled. So the value that condemns the frame sits in the accumulator from byte 9 onward and is never consulted. A peer that declares 16777215 and dribbles the payload without finishing gets the same buffering with no reaction at all, since an incomplete frame never reaches processFrame. RFC 9113 4.2 requires treating an oversized frame as a connection error and explicitly permits responding without reading the rest of the payload. ### Impact Uncontrolled resource consumption leading to unauthenticated remote denial of service by memory exhaustion. - ember-server built .withHttp2: any peer able to open an HTTP/2 connection can trigger it. No authentication and no valid request, since the frame is rejected before it is associated with a stream, and the incomplete variant is never rejected. - ember-client built .withHttp2 against a hostile origin: readLoop is shared, so the client side is symmetric. Reasoned from the shared code path, not reproduced. - Not affected: HTTP/2 off, which is the default on both builders. The overshoot is not configurable. It comes from the protocol's length field, not from Ember's limit, so tuning SETTINGS_MAX_FRAME_SIZE down does not reduce exposure, and withIdleTimeout does not apply because the read loop is making steady progress. Workarounds: leave HTTP/2 off, or terminate it at a proxy that enforces frame size and speak HTTP/1.1 to Ember.

CVE-2026-88975 Affected Http4s Versions

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

References

Frequently Asked Questions

What is CVE-2026-88975?
CVE-2026-88975 is a security vulnerability in Http4s involving Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE under CWE-400: Uncontrolled Resource Consumption.
Which Http4s versions are affected?
Affected versions include releases prior to 0.23.37, 1.0.0-M48 across affected packages: org.http4s:http4s-ember-core_2.13, org.http4s:http4s-ember-core_2.12, org.http4s:http4s-ember-core_3.
What version fixes CVE-2026-88975?
Upgrading to 0.23.37, 1.0.0-M48 (or the latest patched release for your respective branch) resolves the vulnerability.
Is http4s-ember-core_2.13 affected?
Yes, org.http4s:http4s-ember-core_2.13 is affected in releases prior to 0.23.37, 1.0.0-M48. Upgrade your dependency to 0.23.37, 1.0.0-M48 or later.
Is http4s-ember-core_2.12 affected?
Yes, org.http4s:http4s-ember-core_2.12 is affected in releases prior to 0.23.37. Upgrade your dependency to 0.23.37 or later.
What is the CVSS score of CVE-2026-88975?
CVE-2026-88975 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-88975?
CVE-2026-88975 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Maven dependencies for CVE-2026-88975?
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-gq9p-f254-h286",
  "modified" : "2026-09-15T20:01:22Z",
  "published" : "2026-09-15T20:01:22Z",
  "aliases" : [ "CVE-2026-88975" ],
  "summary" : "Http4s: Ember HTTP/2 buffers a frame's declared payload before checking SETTINGS_MAX_FRAME_SIZE",
  "details" : "### Summary\nAn unauthenticated peer can make Ember's HTTP/2 read loop hold 16 MiB of a single frame in memory on a connection where Ember advertised a 16 KiB limit. The declared length is readable from the frame's first 9 bytes, but it is not compared against SETTINGS_MAX_FRAME_SIZE until the whole payload has been read into a contiguous buffer. That is 1024x amplification per connection, bounded by the protocol's 24-bit length field rather than by any setting, and at the default maxConnections of 1024 it puts about 16 GiB of heap in reach.\n\n### Details\nH2Frame.RawFrame.fromByteVector (ember-core/.../h2/H2Frame.scala:66-69) reads the length, then refuses to produce a frame until 9 + length bytes are present:\n\n```\nval length = (bv(2) & 0xff) | ((bv(1) & 0xff) << 8) | ((bv(0) & 0xff) << 16)\nif (bv.length >= 9 + length) {\n```\n\nreadNextFrame in H2Connection.readLoop (H2Connection.scala:246-266) reads that None as \"need more\" and concatenates further socket reads into one accumulator until it is satisfied.\n\nThe only check of an inbound frame against the connection's own SETTINGS_MAX_FRAME_SIZE is in processFrame at H2Connection.scala:534, which cannot run until the frame is assembled. So the value that condemns the frame sits in the accumulator from byte 9 onward and is never consulted. A peer that declares 16777215 and dribbles the payload without finishing gets the same buffering with no reaction at all, since an incomplete frame never reaches processFrame.\n\nRFC 9113 4.2 requires treating an oversized frame as a connection error and explicitly permits responding without reading the rest of the payload.\n\n### Impact\nUncontrolled resource consumption leading to unauthenticated remote denial of service by memory exhaustion.\n\n- ember-server built .withHttp2: any peer able to open an HTTP/2 connection can trigger it. No authentication and no valid request, since the frame is rejected before it is associated with a stream, and the incomplete variant is never rejected.\n- ember-client built .withHttp2 against a hostile origin: readLoop is shared, so the client side is symmetric. Reasoned from the shared code path, not reproduced.\n- Not affected: HTTP/2 off, which is the default on both builders.\n\nThe overshoot is not configurable. It comes from the protocol's length field, not from Ember's limit, so tuning SETTINGS_MAX_FRAME_SIZE down does not reduce exposure, and withIdleTimeout does not apply because the read loop is making steady progress. Workarounds: leave HTTP/2 off, or terminate it at a proxy that enforces frame size and speak 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.13"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.37"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.36"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_2.12"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.37"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.36"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.37"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.23.36"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_2.13"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0-M1"
      }, {
        "fixed" : "1.0.0-M48"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.0-M47"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.http4s:http4s-ember-core_3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0-M1"
      }, {
        "fixed" : "1.0.0-M48"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.0.0-M47"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/security/advisories/GHSA-gq9p-f254-h286"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/commit/87cf334fa3f608ef7d3eb359e71e037ba3336d29"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/http4s/http4s"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/releases/tag/v0.23.37"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/http4s/http4s/releases/tag/v1.0.0-M48"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-15T20:01:22Z",
    "nvd_published_at" : null
  }
}