Complete end-of-life dates, support windows, and security status for all Solr versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.4.1 | Dec 22, 2006 | Supported indefinitely | Supported | Active |
| 3 | 3.6.2 | Mar 30, 2011 | Supported indefinitely | Supported | Active |
| 4 | 4.10.4 | Oct 11, 2012 | Supported indefinitely | Supported | Active |
| 5 | 5.5.5 | Feb 19, 2015 | Oct 24, 2017 | 3119 days past EOL | EOL |
| 6 | 6.6.6 | Apr 7, 2016 | Mar 13, 2019 | 2614 days past EOL | EOL |
| 7 | 7.7.3 | Sep 18, 2017 | May 11, 2022 | 1459 days past EOL | EOL |
| 8 | 8.11.4 | Mar 13, 2019 | Oct 25, 2024 | 561 days past EOL | EOL |
| 9 | 9.10.1 | May 11, 2022 | Already EOL | Supported | Active |
| 10 | 10.0.0 | Mar 3, 2026 | Already EOL | Supported | Active |
When a Solr version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Solr should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →