Eclipse Jetty vulnerabilities: known CVEs & security history
Eclipse · Web / Server · 47 tracked CVEs · 1 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Eclipse Jetty release lines — 47 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Eclipse Jetty's current status and the safe version to run.
Known Eclipse Jetty CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2017-7658 | critical | 9.8 | 21% | 2018 |
| CVE-2017-7657 | critical | 9.8 | 16% | 2018 |
| CVE-2016-4800 | critical | 9.8 | 6% | 2017 |
| CVE-2019-17638 | critical | 9.4 | 11% | 2020 |
| CVE-2018-12538 | high | 8.8 | 3% | 2018 |
| CVE-2026-1605 | high | 7.5 | 0% | 2026 |
| CVE-2025-5115 | high | 7.5 | 2% | 2025 |
| CVE-2025-1948 | high | 7.5 | 1% | 2025 |
| CVE-2024-22201 | high | 7.5 | 1% | 2024 |
| CVE-2023-36478 | high | 7.5 | 4% | 2023 |
| CVE-2022-2191 | high | 7.5 | 2% | 2022 |
| CVE-2022-2048 | high | 7.5 | 2% | 2022 |
| CVE-2021-28165 | high | 7.5 | 54% | 2021 |
| CVE-2009-5045 | high | 7.5 | 2% | 2019 |
| CVE-2018-12545 | high | 7.5 | 5% | 2019 |
| CVE-2017-7656 | high | 7.5 | 6% | 2018 |
| CVE-2017-9735 | high | 7.5 | 6% | 2017 |
| CVE-2015-2080 | high | 7.5 | 75% | 2016 |
| CVE-2026-2332 | high | 7.4 | 0% | 2026 |
| CVE-2026-5795 | high | 7.4 | 0% | 2026 |
| CVE-2024-13009 | high | 7.2 | 0% | 2025 |
| CVE-2020-27216 | high | 7 | 4% | 2020 |
| CVE-2019-17632 | medium | 6.1 | 2% | 2019 |
| CVE-2009-5046 | medium | 6.1 | 2% | 2019 |
| CVE-2019-10241 | medium | 6.1 | 10% | 2019 |
| CVE-2024-8184 | medium | 5.9 | 1% | 2024 |
| CVE-2024-9823 | medium | 5.3 | 1% | 2024 |
| CVE-2023-40167 | medium | 5.3 | 1% | 2023 |
| CVE-2023-26048 | medium | 5.3 | 3% | 2023 |
| CVE-2021-34429 | medium | 5.3 | 99% | 2021 |
| CVE-2021-28169 | medium | 5.3 | 78% | 2021 |
| CVE-2021-28164 | medium | 5.3 | 82% | 2021 |
| CVE-2019-10247 | medium | 5.3 | 6% | 2019 |
| CVE-2019-10246 | medium | 5.3 | 4% | 2019 |
| CVE-2018-12536 | medium | 5.3 | 4% | 2018 |
| CVE-2020-27223 | medium | 5.2 | 78% | 2021 |
| CVE-2020-27218 | medium | 4.8 | 8% | 2020 |
| CVE-2025-11143 | low | 3.7 | 0% | 2026 |
| CVE-2024-6763 | low | 3.7 | 1% | 2024 |
| CVE-2023-41900 | low | 3.5 | 1% | 2023 |
| CVE-2023-36479 | low | 3.5 | 1% | 2023 |
| CVE-2024-6762 | low | 3.1 | 1% | 2024 |
| CVE-2021-34428 | low | 2.9 | 1% | 2021 |
| CVE-2022-2047 | low | 2.7 | 1% | 2022 |
| CVE-2021-28163 | low | 2.7 | 4% | 2021 |
| CVE-2023-26049 | low | 2.4 | 1% | 2023 |
Is my Eclipse Jetty version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Eclipse Jetty version → · Monitor Eclipse Jetty for new CVEs →
Eclipse Jetty vulnerabilities — frequently asked
How many known vulnerabilities does Eclipse Jetty have?
IsItPatched tracks 47 CVEs for Eclipse Jetty, 1 of which is actively exploited (CISA KEV). 4 are critical-severity and 19 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Eclipse Jetty have any actively-exploited vulnerabilities?
Yes — 1 Eclipse Jetty CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild. Patch it as a priority.
What is the most severe Eclipse Jetty vulnerability?
Among tracked issues, CVE-2023-44487 (HIGH, CVSS 7.5), which is actively exploited, ranks highest — a Uncontrolled resource consumption weakness.
Is Eclipse Jetty safe to use?
It depends on the version. The latest supported Eclipse Jetty release (12.1.10) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Eclipse Jetty security status · Eclipse Jetty end-of-life · actively-exploited CVEs. Always verify against Eclipse's advisories — see our disclaimer.