CVE-2024-6762: Org.eclipse.jetty:jetty servlets: Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks
Affects org.eclipse.jetty:jetty-servletsSource GCVE Database
Not known to be exploited · CVSS 3.1 Low : upgrade to 10.0.18 when convenient.
Data as of 29 Oct 2026, 22:52 UTC
Thin evidence
One scorer or none| CNA (eclipse) | CVSS 3.1 | 3.1 |
|---|
- Patch
- Available – fixed in 10.0.18, 11.0.18, 12.0.4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade org.eclipse.jetty:jetty-servlets to 10.0.18; org.eclipse.jetty:jetty-servlets to 11.0.18; org.eclipse.jetty:jetty-servlets to 12.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.eclipse.jetty:jetty-servlets | Affected
| Fixed in
|
| Mavenorg.eclipse.jetty:jetty-servlets | Affected
| Fixed in
|
| Mavenorg.eclipse.jetty:jetty-servlets | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact Jetty PushSessionCacheFilter can be exploited by unauthenticated users to launch remote DoS attacks by exhausting the server’s memory. ### Patches * https://github.com/jetty/jetty.project/pull/9715 * https://github.com/jetty/jetty.project/pull/9716 ### Workarounds The session usage is intrinsic to the design of the PushCacheFilter. The issue can be avoided by: + not using the PushCacheFilter. Push has been deprecated by the various IETF specs and early hints responses should be used instead. + reducing the reducing the idle timeout on unauthenticated sessions will reduce the time such session stay in memory. + configuring a session cache to use [session passivation](https://jetty.org/docs/jetty/12/programming-guide/server/session.html), so that sessions are not stored in memory, but rather in a database or file system that may have significantly more capacity than memory. ### References * https://github.com/jetty/jetty.project/pull/10756 * https://github.com/jetty/jetty.project/pull/10755
References
- github.com/jetty/jetty.project/security/advisories/GHSA-r7m4-f9h5-gr79 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2024-6762 (opens in a new tab)
- github.com/jetty/jetty.project/pull/10755 (opens in a new tab)
- github.com/jetty/jetty.project/pull/10756 (opens in a new tab)
- github.com/jetty/jetty.project/pull/9715 (opens in a new tab)
- github.com/jetty/jetty.project/pull/9716 (opens in a new tab)
- github.com/jetty/jetty.project (opens in a new tab)
- gitlab.eclipse.org/security/cve-assignement/-/issues/24 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/04/msg00001.html (opens in a new tab)