How severe is GHSA-r7m4-f9h5-gr79?

GHSA-r7m4-f9h5-gr79 has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r7m4-f9h5-gr79?

GHSA-r7m4-f9h5-gr79 affects the following packages: org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven), org.eclipse.jetty:jetty-servlets (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r7m4-f9h5-gr79?

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.

How do I detect GHSA-r7m4-f9h5-gr79 in my Maven dependencies?

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.

How do I mitigate GHSA-r7m4-f9h5-gr79 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 GHSA-r7m4-f9h5-gr79 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r7m4-f9h5-gr79 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 GHSA-r7m4-f9h5-gr79?

GHSA-r7m4-f9h5-gr79 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th 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 GHSA-r7m4-f9h5-gr79?

GHSA-r7m4-f9h5-gr79 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r7m4-f9h5-gr79 published, and has it been updated?

GHSA-r7m4-f9h5-gr79 was published on October 14, 2024 and was last updated on November 3, 2025. 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

LOW severity

Eclipse Jetty's PushSessionCacheFilter can cause remote DoS attacksGHSA-r7m4-f9h5-gr79

LOWFix: jetty/jetty.project#10755

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.

Also known asCVE-2024-6762

Published

Oct 14, 2024

Updated

Nov 3, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

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

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets☕org.eclipse.jetty:jetty-servlets

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

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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 10.0.0&&< 10.0.18	10.0.18`org.eclipse.jetty:jetty-servlets:10.0.18`
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 11.0.0&&< 11.0.18	11.0.18`org.eclipse.jetty:jetty-servlets:11.0.18`
☕Maven	`org.eclipse.jetty:jetty-servlets`	≥ 12.0.0&&< 12.0.4	12.0.4`org.eclipse.jetty:jetty-servlets:12.0.4`

Affected Products

1 product · 3 configurations

Application

jettyeclipse

≥ 12.0.0 && < 12.0.4

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

Frequently Asked Questions

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