Splunk · Lifecycle Status

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.

Splunk 9.3 reaches end of life on July 24, 2026. Plan your migration now — 76 days remaining.
Latest Active
9.4.7
9.4 series
Next EOL
9.3
Jul 24, 2026
Active Versions
2
of 13 total
EOL Versions
10
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20182019202020212022202320242025202620277.07.17.27.38.08.18.29.09.19.29.39.410.0TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
7.0 7.0.13.1 Sep 26, 2017 Jan 31, 2020 2290 days past EOL EOL
7.1 7.1.10 Apr 24, 2018 Oct 31, 2020 2016 days past EOL EOL
7.2 7.2.10.1 Oct 2, 2018 Apr 30, 2021 1835 days past EOL EOL
7.3 7.3.9 Jun 4, 2019 Oct 22, 2021 1660 days past EOL EOL
8.0 8.0.10 Oct 22, 2019 Oct 22, 2021 1660 days past EOL EOL
8.1 8.1.14 Oct 20, 2020 Apr 19, 2023 1116 days past EOL EOL
8.2 8.2.12 May 12, 2021 May 12, 2023 1093 days past EOL EOL
9.0 9.0.10 Jun 14, 2022 Jun 14, 2024 694 days past EOL EOL
9.1 9.1.10 Jun 28, 2023 Jun 28, 2025 315 days past EOL EOL
9.2 9.2.11 Jan 31, 2024 Jan 31, 2026 98 days past EOL EOL
9.3 9.3.8 Jul 24, 2024 Jul 24, 2026 76 days remaining Warning
9.4 9.4.7 Dec 16, 2024 Dec 16, 2026 221 days remaining Active
10.0 10.0.2 Jul 28, 2025 Jul 28, 2027 445 days remaining Active

What does Splunk end of life mean for your organization?

When a Splunk 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 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Splunk?
The next Splunk version reaching EOL is 9.3 on July 24, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Splunk?
The latest active version of Splunk is 9.4.7. Always verify against the table above as support windows can change.
What happens when Splunk reaches end of life?
When Splunk reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Splunk?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Splunk versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →