Solr 4 · Version Status

Solr 4 End of Life Date

Solr 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Solr 4 is actively supported. EOL date: Supported indefinitely.
EOL Date
Supported indefinitely
Supported
Latest Release
4.10.4
Standard release
Release Date
Oct 11, 2012
Solr 4 series
← Solr 3 All Solr versions Solr 5 →
All Solr Versions
VersionLatestEOL DateStatus
1 1.4.1 Supported Active
3 3.6.2 Supported Active
4 4.10.4 Supported Active
5 5.5.5 Oct 24, 2017 EOL
6 6.6.6 Mar 13, 2019 EOL
7 7.7.3 May 11, 2022 EOL
8 8.11.4 Oct 25, 2024 EOL
9 9.10.1 EOL Active

What does Solr 4 end of life mean?

When Solr 4 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Solr 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Solr 10 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Solr 4 reach end of life?
Solr 4 has no scheduled end-of-life date and is supported indefinitely.
Is Solr 4 still supported?
Yes, Solr 4 is currently supported. The EOL date is Supported indefinitely.
What should I upgrade to from Solr 4?
The recommended upgrade from Solr 4 is Solr 10 — the latest actively supported version. Check the Solr full timeline for all supported versions.
What are the security risks of running Solr 4 past EOL?
When Solr 4 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Solr should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →