Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-6762: 0.94% estimated exploitation activity in the next 30 days; percentile 61.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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, 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

Published by the source

14 Oct 2024, 21:07 UTC

Last modified by the source

3 Nov 2025, 22:49 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r7m4-f9h5-gr79

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-6762

Advisory: Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks
IDs: CVE-2024-6762, GHSA-r7m4-f9h5-gr79
Record: https://patchnext.com/advisories/cve-2024-6762 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty:jetty-servlets 12.0.4, 11.0.18, 10.0.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty:jetty-servlets: affected >= 10.0.0, <= 10.0.17; >= 11.0.0, <= 11.0.17; >= 12.0.0, <= 12.0.3; fixed in 12.0.4, 10.0.18, 11.0.18

## Suggested inspection (read-only)
- Maven org.eclipse.jetty:jetty-servlets: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty:jetty-servlets.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r7m4-f9h5-gr79 (GitHub-reviewed advisory GHSA-r7m4-f9h5-gr79 lists affected ranges: Maven org.eclipse.jetty:jetty-servlets >=10.0.0 =11.0.0 =12.0.0 <=12.0.3)

Commands are suggestions: review each one before running it.