Elasticsearch 7.17 end of life
Elasticsearch 7.17 end of life was 15 January 2026, after Elastic ended maintenance on 15 April 2025. The last release was 7.17.29, published on 24 June 2025. Four advisories published since, including CVE-2025-37731 and CVE-2025-68384, name the 7.x line and were fixed only in 8.19 and 9.x. Elastic ends 8.x maintenance on 15 January 2027.
What now
Which vendors provide Elasticsearch 7.17 security patches now that support has ended?
Elasticsearch 7.17 After EOL: Patched 7.x or OpenSearch- End of life
- 15 January 2026
- Released
- Feb 2022
- Final release
- 7.17.29
- Successor
- Elasticsearch 8.19 or 9.x, or OpenSearch
Date published by Elastic product end of life dates. We do not publish a lifecycle date we cannot source. Dates checked on elastic.co/support/eol and endoflife.date on 20 October 2026.
Last reviewed
Elasticsearch versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| Elasticsearch 8.x | 10 Feb 2022 | 15 July 2027 | Approaching |
| Elasticsearch 7.17 (this page) | 1 Feb 2022 | 15 January 2026 | End of life |
| Elasticsearch 7.10 | 11 Nov 2020 | 11 May 2022 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 15 January 2026
- Releases on the 7.17 line. 7.17.29 was the last.
- Security fixes. CVE-2025-37731 and CVE-2025-68384 have no 7.x fix.
- Elastic support for 7.17 under standard subscriptions.
What actually breaks in the upgrade
Indices from 6.x must be reindexed
An Elasticsearch 8.0 node will not start with indices created before 7.0. Reindex them on 7.17 first; for large clusters this is the longest part of the upgrade.
Security is on by default in 8.x
8.x enables TLS and authentication on first start and removes mapping types. Clients, ingest pipelines and dashboards all need testing against the new defaults.
CVEs published since the last Elasticsearch 7.17 release
These are the CVEs in OSSeva's CVE directory that name the 7.x line and were published after 7.17.29 (24 June 2025). Elastic fixed each in 8.19.x and 9.x only. None is scored 9.0 or higher.
4 in the directory as of 20 October 2026.
| CVE | CVSS | Published | Issue | Fixed upstream in |
|---|---|---|---|---|
| CVE-2025-37727 | 5.7 | 10 Oct 2025 | Elasticsearch: audit logging can record reindex request bodies containing sensitive data | 8.19.5, 9.0.8 and later |
| CVE-2025-37731 | 7.4 | 15 Dec 2025 | Elasticsearch PKI realm: user impersonation through crafted client certificates | 8.19.8, 9.1.8 and later |
| CVE-2025-68384 | 6.5 | 18 Dec 2025 | Elasticsearch: low-privileged user can crash a node with oversized user settings | 8.19.9, 9.1.9 and later |
| CVE-2026-72683 | 6.5 | 13 Aug 2026 | Elasticsearch: simulate pipeline request causes unbounded recursion and kills the node | 8.19.19, 9.3.8 and later |
The directory lists Elasticsearch CVEs matched at NVD to the product, mostly with a CVSS score of 7.0 or higher, so it is a subset of every advisory. A CVE is listed when its MITRE record names 7.x and it was published after the last 7.17 release. Fixed-in versions are from Elastic's advisories; none is a 7.x release.
Elasticsearch 8.x or OpenSearch: what blocks each move
Both routes start from the same inventory of indices, mappings, plugins, pipelines and clients. The solution page lists the 7.17 features that most often decide the route, with what 8.x and OpenSearch each do about them.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 8.19 or 9.x | Reindex old indices, update clients, enable security. | Scales with index count, clients and plugins | Engineering time and Elastic licence terms | The Elastic path. |
| Migrate to OpenSearch | The Apache-2.0 fork of 7.10.2. | Scales with index count, clients and the pieces that do not carry over | Migration | The open source licence path. |
| OSSeva patched builds on 7.17 | Backported fixes for self-managed 7.17: Critical 48 hours, High 7 days. | Starts from your current version | Subscription, priced per cluster | For clusters waiting on a reindex window. |
What OSSeva does for Elasticsearch 7.17
OSSeva patches this line
OSSeva patches self-managed Elasticsearch 7.10.2 and 7.17 and runs migrations to 8.x or OpenSearch.
Elasticsearch extended supportWhat your auditor will say
Requirement 6.3.3. Search clusters that index cardholder or log data are in scope.
When did Elasticsearch 7.17 reach end of life?
On 15 January 2026. Maintenance ended on 15 April 2025, and the last release was 7.17.29 on 24 June 2025.
When does Elasticsearch 8.x reach end of life?
Elastic lists end of maintenance for 8.x on 15 January 2027 and end of life on 15 July 2027.
Which CVEs affect Elasticsearch 7.17 since it ended?
The table above lists the four in OSSeva's CVE directory that name 7.x and were published after the last 7.17 release. Elastic fixed each in 8.19.x and 9.x only.
Can I upgrade Elasticsearch 7.17 straight to 8.x?
Yes, if every index was created in 7.x. Indices created in 6.x or earlier must be reindexed first.
Get a quote
Still running Elasticsearch 7.17?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?