# CVE-2025-1948: Eclipse Jetty HTTP clients can increase memory allocation

> An attacker can cause a denial of service by sending a large HTTP/2 header size setting, forcing the server to exhaust memory.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** CLEANSTART-2026-EO53976, CLEANSTART-2026-MS35151, DEBIAN-CVE-2025-1948, GHSA-889j-63jv-qhr8, MINI-cvqq-pphf-wj8m, ROOT-APP-MAVEN-CVE-2025-1948, UBUNTU-CVE-2025-1948

## What is CVE-2025-1948?

CVE-2025-1948 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-1948?

2 open source packages ship an affected version, including org.eclipse.jetty.http2:jetty-http2-common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty.http2:jetty-http2-common` | Maven | From 12.0.0 | 12.0.17 |
| `org.eclipse.jetty.http2:jetty-http2-common` | Maven | From 12.0.0 | 12.0.17 |

Products: Eclipse Jetty.

## How do I fix CVE-2025-1948?

Upgrade org.eclipse.jetty.http2:jetty-http2-common to 12.0.17 or later.

## Is CVE-2025-1948 being exploited?

There is no known exploitation of CVE-2025-1948 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Jetty

- [CVE-2016-4800](https://insights.sbomify.com/CVE-2016-4800/): Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request (critical 9.8)
- [CVE-2019-17638](https://insights.sbomify.com/CVE-2019-17638/): Operation on a Resource after Expiration or Release in Jetty Server (critical 9.4)
- [CVE-2018-12538](https://insights.sbomify.com/CVE-2018-12538/): Access and integrity issue within Eclipse Jetty (high 8.8)
- [CVE-2026-10050](https://insights.sbomify.com/CVE-2026-10050/): Digest authentication lossy encoding (high 8.7)
- [CVE-2025-5115](https://insights.sbomify.com/CVE-2025-5115/): MadeYouReset HTTP/2 vulnerability (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1948 and fix it if it is affected.

What it is: CVE-2025-1948 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1948 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty.http2:jetty-http2-common (Maven): affected from 12.0.0; fixed in 12.0.17
- org.eclipse.jetty.http2:jetty-http2-common (Maven): affected from 12.0.0; fixed in 12.0.17

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1948/ (Markdown: https://insights.sbomify.com/CVE-2025-1948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1948
- OSV: https://osv.dev/vulnerability/CVE-2025-1948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1948/
Summaries are generated and may contain mistakes; the official description above is the record.