GHSA-r7m4-f9h5-gr79 is a low-severity (CVSS 3.1) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty:jetty-servlets. A fix is available for org.eclipse.jetty:jetty-servlets — see the affected versions and patch details below.
Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacks
Exploitation Status
No confirmed exploitation observed yet
- 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 GHSA-r7m4-f9h5-gr79.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-r7m4-f9h5-gr79 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servletsReal-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
Jetty PushSessionCacheFilter can be exploited by unauthenticated users to launch remote DoS attacks by exhausting the server’s memory.
Patches
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 10.0.0&&< 10.0.18 | 10.0.18org.eclipse.jetty:jetty-servlets:10.0.18 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 11.0.0&&< 11.0.18 | 11.0.18org.eclipse.jetty:jetty-servlets:11.0.18 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 12.0.0&&< 12.0.4 | 12.0.4org.eclipse.jetty:jetty-servlets:12.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-servlets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-servlets to 10.0.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7m4-f9h5-gr79 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r7m4-f9h5-gr79 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r7m4-f9h5-gr79. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r7m4-f9h5-gr79 in your dependencies?
O3 Security finds GHSA-r7m4-f9h5-gr79 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.