# CVE-2024-7708: Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests

> Attackers can cause a buffer leak in Eclipse Jetty by sending requests with bodies that read zero bytes, leading to resource exhaustion and denial of service.

- **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:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** CLEANSTART-2026-MF87519, CLSA-2026-1785292544, DEBIAN-CVE-2024-7708, GHSA-9299-c6m4-mjhc, MINI-87r4-vv3w-39r4, UBUNTU-CVE-2024-7708

## What is CVE-2024-7708?

CVE-2024-7708 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak.
This is particularly the case for 100-Continue, but any request where the network is slow can leak.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-7708?

4 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.jetty:jetty-server` | Maven | From 10.0.7 | 10.0.23 |
| `org.eclipse.jetty:jetty-server` | Maven | From 10.0.7 | 10.0.23 |
| `org.eclipse.jetty:jetty-server` | Maven | From 11.0.7 | 11.0.23 |
| `org.eclipse.jetty:jetty-server` | Maven | From 11.0.7 | 11.0.23 |

Products: Eclipse Jetty.

## How do I fix CVE-2024-7708?

Upgrade org.eclipse.jetty:jetty-server to a fixed version for your release line: 10.0.23 or 11.0.23.

## Is CVE-2024-7708 being exploited?

There is no known exploitation of CVE-2024-7708 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-2024-7708 and fix it if it is affected.

What it is: CVE-2024-7708 is a high-severity denial of service vulnerability in Eclipse Jetty, published on 14 Jul 2026. 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-2024-7708 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.jetty:jetty-server (Maven): affected from 10.0.7; fixed in 10.0.23
- org.eclipse.jetty:jetty-server (Maven): affected from 10.0.7; fixed in 10.0.23
- org.eclipse.jetty:jetty-server (Maven): affected from 11.0.7; fixed in 11.0.23
- org.eclipse.jetty:jetty-server (Maven): affected from 11.0.7; fixed in 11.0.23

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-2024-7708/ (Markdown: https://insights.sbomify.com/CVE-2024-7708/index.md)
```

## Sources

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

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