Splunk End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Splunk versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.0 | 7.0.13.1 | Sep 26, 2017 | Jan 31, 2020 | 2335 days past EOL | EOL |
| 7.1 | 7.1.10 | Apr 24, 2018 | Oct 31, 2020 | 2061 days past EOL | EOL |
| 7.2 | 7.2.10.1 | Oct 2, 2018 | Apr 30, 2021 | 1880 days past EOL | EOL |
| 7.3 | 7.3.9 | Jun 4, 2019 | Oct 22, 2021 | 1705 days past EOL | EOL |
| 8.0 | 8.0.10 | Oct 22, 2019 | Oct 22, 2021 | 1705 days past EOL | EOL |
| 8.1 | 8.1.14 | Oct 20, 2020 | Apr 19, 2023 | 1161 days past EOL | EOL |
| 8.2 | 8.2.12 | May 12, 2021 | May 12, 2023 | 1138 days past EOL | EOL |
| 9.0 | 9.0.10 | Jun 14, 2022 | Jun 14, 2024 | 739 days past EOL | EOL |
| 9.1 | 9.1.10 | Jun 28, 2023 | Jun 28, 2025 | 360 days past EOL | EOL |
| 9.2 | 9.2.12 | Jan 31, 2024 | Jan 31, 2026 | 143 days past EOL | EOL |
| 9.3 | 9.3.13 | Jul 24, 2024 | Jul 24, 2026 | 31 days remaining | Warning |
| 9.4 | 9.4.12 | Dec 16, 2024 | Dec 16, 2026 | 176 days remaining | Warning |
| 10.0 | 10.0.7 | Jul 28, 2025 | Jul 28, 2027 | 400 days remaining | Active |
| 10.2 | 10.2.4 | Jan 15, 2026 | Jan 15, 2028 | 571 days remaining | Active |
| 10.4 | 10.4.0 | May 18, 2026 | May 18, 2028 | 695 days remaining | Active |
What does Splunk end of life mean for your organization?
When a version of Splunk 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 Splunk 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Splunk versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →