CVE-2025-1948: Jetty http2 common Remote Code Execution Vulnerability
HIGHCVE-2025-1948 is a HIGH (CVSS 7.5) remote code execution vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Jetty http2 common libraries in the Maven ecosystem. The issue involves eclipse jetty http/2 client can force the server to allocate a humongous byte buffer that may lead to oom and subsequently the jvm to exit. Remediation is available by upgrading affected packages to version 12.0.17.
CVE-2025-1948 at a Glance
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).
How to Fix CVE-2025-1948
To remediate this vulnerability, upgrade all affected Jetty http2 common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.eclipse.jetty.http2</groupId>
<artifactId>jetty-http2-common</artifactId>
<version>12.0.17</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.eclipse.jetty.http2
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2025-1948, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.eclipse.jetty.http2
Analyze the terminal output to locate any version of Jetty http2 common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 12.0.17), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.eclipse.jetty.http2 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 Jetty http2 common, 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
CVE-2025-1948 Affected Jetty http2 common Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.eclipse.jetty.http2:jetty-http2-common
|
Maven |
≥ 12.0.0
< 12.0.17
|
12.0.17
|
References
Frequently Asked Questions
What is CVE-2025-1948?
Which Jetty http2 common versions are affected?
What version fixes CVE-2025-1948?
Is jetty-http2-common affected?
What is the CVSS score of CVE-2025-1948?
What CWE is associated with CVE-2025-1948?
How can I check Maven dependencies for CVE-2025-1948?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-889j-63jv-qhr8",
"modified" : "2025-05-08T19:28:45Z",
"published" : "2025-05-08T19:28:45Z",
"aliases" : [ "CVE-2025-1948" ],
"summary" : "Eclipse Jetty HTTP/2 client can force the server to allocate a humongous byte buffer that may lead to OoM and subsequently the JVM to exit",
"details" : "### Original Report\n\nIn Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can specify a very large value for the HTTP/2 settings parameter SETTINGS_MAX_HEADER_LIST_SIZE. The Jetty HTTP/2 server does not perform validation on this setting, and tries to allocate a ByteBuffer of the specified capacity to encode HTTP responses, likely resulting in OutOfMemoryError being thrown, or even the JVM process exiting.\n\n### Impact\nRemote peers can cause the JVM to crash or continuously report OOM.\n\n### Patches\n12.0.17\n\n### Workarounds\nNo workarounds.\n\n### References\nhttps://github.com/jetty/jetty.project/issues/12690",
"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.eclipse.jetty.http2:jetty-http2-common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "12.0.0"
}, {
"fixed" : "12.0.17"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 12.0.16"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/jetty/jetty.project/security/advisories/GHSA-889j-63jv-qhr8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-1948"
}, {
"type" : "WEB",
"url" : "https://github.com/jetty/jetty.project/issues/12690"
}, {
"type" : "WEB",
"url" : "https://github.com/jetty/jetty.project/commit/c8c2515936ef968dc8a3cecd9e79d1e69291e4bb"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jetty/jetty.project"
}, {
"type" : "WEB",
"url" : "https://gitlab.eclipse.org/security/cve-assignement/-/issues/56"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-05-08T19:28:45Z",
"nvd_published_at" : "2025-05-08T18:15:41Z"
}
}