GHSA-j26w-f9rq-mr2q
MEDIUMEclipse Jetty has a denial of service vulnerability on DosFilter
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.
Blast Radius
org.eclipse.jetty.ee10:jetty-ee10-servlets☕org.eclipse.jetty.ee8:jetty-ee8-servlets☕org.eclipse.jetty.ee9:jetty-ee9-servlets☕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
Description There exists a security vulnerability in Jetty's DosFilter which can be exploited by unauthorized users to cause remote denial-of-service (DoS) attack on the server using DosFilter. By repeatedly sending crafted requests, attackers can trigger OutofMemory errors and exhaust the server's memory finally.
Vulnerability details The Jetty DoSFilter (Denial of Service Filter) is a security filter designed to protect web applications against certain types of Denial of Service (DoS) attacks and other abusive behavior. It helps to mitigate excessive resource consumption by limiting the rate at which clients can make requests to the server. The DoSFilter monitors and tracks client request patterns, including request rates, and can take actions such as blocking or delaying requests from clients that exceed predefined thresholds. The internal tracking of requests in DoSFilter is the source of this OutOfMemory condition.
Impact Users of the DoSFilter may be subject to DoS attacks that will ultimately exhaust the memory of the server if they have not configured session passivation or an aggressive session inactivation timeout.
Patches The DoSFilter has been patched in all active releases to no longer support the session tracking mode, even if configured.
Patched releases:
- 9.4.54
- 10.0.18
- 11.0.18
- 12.0.3
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.jetty.ee10:jetty-ee10-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3 |
| ☕Maven | org.eclipse.jetty.ee8:jetty-ee8-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3 |
| ☕Maven | org.eclipse.jetty.ee9:jetty-ee9-servlets | ≥ 12.0.0&&< 12.0.3 | 12.0.3 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 9.0.0&&< 9.4.54 | 9.4.54 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 10.0.0&&< 10.0.18 | 10.0.18 |
| ☕Maven | org.eclipse.jetty:jetty-servlets | ≥ 11.0.0&&< 11.0.18 | 11.0.18 |
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.ee10:jetty-ee10-servlets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.jetty.ee10:jetty-ee10-servlets to 12.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j26w-f9rq-mr2q 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 pinpoints whether GHSA-j26w-f9rq-mr2q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-j26w-f9rq-mr2q. 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-j26w-f9rq-mr2q in your dependencies?
O3 detects GHSA-j26w-f9rq-mr2q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.