Elasticsearch 7 · Version Status
Elasticsearch 7 End of Life Date
Elasticsearch 7 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Elasticsearch 7 is past end of life. This version no longer receives security patches. 296 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 15, 2026
296 days past EOL
Latest Release
7.17.29
Standard release
Release Date
Apr 10, 2019
Elasticsearch 7 series
Where these dates come from
End of lifeJan 15, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseApr 10, 2019endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Elasticsearch 7 was released on April 10, 2019 and support ended on January 15, 2026 — a supported lifespan of 6 years and 9 months, longer than the 6 months median for Elasticsearch releases. Its latest release on record is 7.17.29, published June 24, 2025 — 7 months before support ended. It has been past its end-of-life date for 10 months. 3 newer Elasticsearch releases have shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Elasticsearch 7 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Elasticsearch Versions
| Version | Latest | EOL Date | Status |
|---|
| 6 |
6.8.23 |
Feb 10, 2022 |
EOL |
| → 7 |
7.17.29 |
Jan 15, 2026 |
EOL |
| 8.16 |
8.16.6 |
Apr 15, 2025 |
EOL |
| 8.17 |
8.17.10 |
Jul 29, 2025 |
EOL |
| 9.0 |
9.0.8 |
Oct 23, 2025 |
EOL |
| 8.18 |
8.18.8 |
Oct 23, 2025 |
EOL |
| 8.19 |
8.19.24 |
Jul 15, 2027 |
Active |
| 9.1 |
9.1.10 |
Feb 3, 2026 |
EOL |
What does Elasticsearch 7 end of life mean?
When Elasticsearch 7 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Elasticsearch 7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Elasticsearch 9.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Elasticsearch 7 reach end of life?
Elasticsearch 7 reached end of life on January 15, 2026. This version is no longer receiving security patches.
Is Elasticsearch 7 still supported?
No. Elasticsearch 7 reached end of life on January 15, 2026 and is no longer receiving security patches.
What should I upgrade to from Elasticsearch 7?
The recommended upgrade from Elasticsearch 7 is
Elasticsearch 9.5 — the latest actively supported version. Check the
Elasticsearch full timeline for all supported versions.
What are the security risks of running Elasticsearch 7 past EOL?
Since Elasticsearch 7 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Elasticsearch should migrate immediately or implement compensating controls.