Apache Solr vulnerabilities: known CVEs & security history
Apache · Search · 47 tracked CVEs · 3 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Apache Solr release lines — 47 in total, with 3 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Apache Solr's current status and the safe version to run.
Known Apache Solr 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-2019-17558⚡ exploited | high | 7.5 | 99% | 2019 |
| CVE-2019-0193⚡ exploited | high | 7.2 | 84% | 2019 |
| CVE-2024-45216 | critical | 9.8 | 91% | 2024 |
| CVE-2021-44548 | critical | 9.8 | 5% | 2021 |
| CVE-2021-27905 | critical | 9.8 | 93% | 2021 |
| CVE-2020-13957 | critical | 9.8 | 79% | 2020 |
| CVE-2019-12409 | critical | 9.8 | 22% | 2019 |
| CVE-2019-0192 | critical | 9.8 | 78% | 2019 |
| CVE-2017-12629 | critical | 9.8 | 92% | 2017 |
| CVE-2021-29943 | critical | 9.1 | 5% | 2021 |
| CVE-2017-1000190 | critical | 9.1 | 5% | 2017 |
| CVE-2023-50386 | high | 8.8 | 84% | 2024 |
| CVE-2020-9492 | high | 8.8 | 4% | 2021 |
| CVE-2020-13941 | high | 8.8 | 4% | 2020 |
| CVE-2026-22022 | high | 8.2 | 0% | 2026 |
| CVE-2026-44825 | high | 8.1 | 1% | 2026 |
| CVE-2024-45217 | high | 8.1 | 1% | 2024 |
| CVE-2023-50298 | high | 7.5 | 2% | 2024 |
| CVE-2023-50292 | high | 7.5 | 3% | 2024 |
| CVE-2023-50291 | high | 7.5 | 3% | 2024 |
| CVE-2021-33813 | high | 7.5 | 19% | 2021 |
| CVE-2021-29262 | high | 7.5 | 8% | 2021 |
| CVE-2019-12401 | high | 7.5 | 8% | 2019 |
| CVE-2017-3164 | high | 7.5 | 19% | 2019 |
| CVE-2018-1308 | high | 7.5 | 21% | 2018 |
| CVE-2017-9803 | high | 7.5 | 2% | 2017 |
| CVE-2017-3163 | high | 7.5 | 7% | 2017 |
| CVE-2017-7660 | high | 7.5 | 6% | 2017 |
| CVE-2012-6612 | high | 7.5 | 10% | 2013 |
| CVE-2026-22444 | high | 7.1 | 1% | 2026 |
| CVE-2023-50290 | medium | 6.5 | 69% | 2024 |
| CVE-2013-6408 | medium | 6.4 | 11% | 2013 |
| CVE-2013-6407 | medium | 6.4 | 11% | 2013 |
| CVE-2015-8797 | medium | 6.1 | 3% | 2016 |
| CVE-2015-8796 | medium | 6.1 | 3% | 2016 |
| CVE-2015-8795 | medium | 6.1 | 3% | 2016 |
| CVE-2025-24814 | medium | 5.5 | 1% | 2025 |
| CVE-2018-8026 | medium | 5.5 | 9% | 2018 |
| CVE-2018-8010 | medium | 5.5 | 4% | 2018 |
| CVE-2024-52012 | medium | 5.4 | 41% | 2025 |
| CVE-2020-27223 | medium | 5.2 | 78% | 2021 |
| CVE-2018-11802 | medium | 4.3 | 2% | 2020 |
| CVE-2014-3628 | medium | 4.3 | 5% | 2015 |
| CVE-2013-6397 | medium | 4.3 | 56% | 2013 |
| CVE-2009-3821 | medium | 4.3 | 2% | 2009 |
| CVE-2021-28163 | low | 2.7 | 4% | 2021 |
Is my Apache Solr 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 Apache Solr version → · Monitor Apache Solr for new CVEs →
Apache Solr vulnerabilities — frequently asked
How many known vulnerabilities does Apache Solr have?
IsItPatched tracks 47 CVEs for Apache Solr, 3 of which are actively exploited (CISA KEV). 9 are critical-severity and 22 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Apache Solr have any actively-exploited vulnerabilities?
Yes — 3 Apache Solr CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. Patch these as a priority.
What is the most severe Apache Solr vulnerability?
Among tracked issues, CVE-2023-44487 (HIGH, CVSS 7.5), which is actively exploited, ranks highest — a Uncontrolled resource consumption weakness.
Is Apache Solr safe to use?
It depends on the version. The latest supported Apache Solr release 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: Apache Solr security status · Apache Solr end-of-life · actively-exploited CVEs. Always verify against Apache's advisories — see our disclaimer.