How severe is CVE-2024-7708?

CVE-2024-7708 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-7708?

CVE-2024-7708 affects the following packages: org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-7708?

Update org.eclipse.jetty:jetty-server to 10.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-7708 is resolved across your whole dependency graph.

How do I detect CVE-2024-7708 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-7708 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-7708 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-7708 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-7708?

CVE-2024-7708 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-7708?

CVE-2024-7708 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-401 (CWE-401). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-7708 published, and has it been updated?

CVE-2024-7708 was published on July 14, 2026 and was last updated on October 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2024-7708 — jetty-server

HIGHFix: jetty/jetty.project#12156

CVE-2024-7708 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty:jetty-server. A fix is available for org.eclipse.jetty:jetty-server — see the affected versions and patch details below.

Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests

Also known asGHSA-9299-c6m4-mjhc

Published

Jul 14, 2026

Updated

Oct 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-7708.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2024-7708 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 391,411 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The original report:

Server handling of 100-Continue requests can lead to memory leak that can be abused to cause a Denial of Service state.

After investigation, turns out that every request that has a body, but reading the body may end up in reading 0 bytes, leaks a buffer. This is particularly the case for 100-Continue, but any request where the network is slow can leak.

Affected Versions

Jetty 11.0.0-11.0.22 (EOL)
Jetty 10.0.0-10.0.22 (EOL)

Patched Versions

Jetty 11.0.23
Jetty 10.0.23

Patches

https://github.com/jetty/jetty.project/pull/12156

Workarounds

No workarounds.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 10.0.7&&< 10.0.23	10.0.23`org.eclipse.jetty:jetty-server:10.0.23`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 11.0.7&&< 11.0.23	11.0.23`org.eclipse.jetty:jetty-server:11.0.23`

Affected Products

1 product · 2 configurations

Application

jettyeclipse

≥ 11.0.7 && < 11.0.23

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-server to 10.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-7708 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat's version of Eclipse Jetty (9.0.3) shipped in Red Hat Enterprise Linux 7 is not affected by this vulnerability. The flaw was introduced in Jetty 10.0.0 and affects versions 10.0.0 through 10.0.22 and 11.0.0 through 11.0.22. The shipped version predates the introduction of the vulnerable code.

Workaround published by Red Hat

No mitigation is needed as Red Hat products are not affected by this vulnerability.

Source: Red Hat security advisory for CVE-2024-7708 (CC BY 4.0)

Frequently Asked Questions

### Impact The original report: > Server handling of 100-Continue requests can lead to memory leak that can be abused to cause a Denial of Service state. After investigation, turns out that every request that has a body, but reading the body may end up in reading 0 bytes, leaks a buffer. This is particularly the case for 100-Continue, but any request where the network is slow can leak. ### Affected Versions * Jetty 11.0.0-11.0.22 (EOL) * Jetty 10.0.0-10.0.22 (EOL) ### Patched Versions * Jetty 11.0.23 * Jetty 10.0.23 ### Patches https://github.com/jetty/jetty.project/pull/12156 ### Wor