Skip to content

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

High severity GitHub Reviewed Published Jul 13, 2026 in jetty/jetty.project • Updated Jul 22, 2026

Package

maven org.eclipse.jetty:jetty-server (Maven)

Affected versions

>= 10.0.7, < 10.0.23
>= 11.0.7, < 11.0.23

Patched versions

10.0.23
11.0.23

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

jetty/jetty.project#12156

Workarounds

No workarounds.

References

@sbordet sbordet published to jetty/jetty.project Jul 13, 2026
Published by the National Vulnerability Database Jul 14, 2026
Published to the GitHub Advisory Database Jul 22, 2026
Reviewed Jul 22, 2026
Last updated Jul 22, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(17th percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

Missing Release of Memory after Effective Lifetime

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. Learn more on MITRE.

CVE ID

CVE-2024-7708

GHSA ID

GHSA-9299-c6m4-mjhc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.