Elasticsearch 7.10 end of life
Elasticsearch 7.10 reached end of life on 11 May 2022 under Elastic's product end-of-life policy. Its last release, 7.10.2 on 14 January 2021, is the last Elasticsearch release with Apache 2.0 as the default licence, which is why many clusters stayed on it and OpenSearch was derived from it. OSSeva ships patched builds of the 7.10.2 code.
What now
Which vendors provide Elasticsearch 7.10 security patches now that support has ended?
Elasticsearch 7.17 After EOL: Patched 7.x or OpenSearch- End of life
- 11 May 2022
- Released
- Nov 2020
- Final release
- 7.10.2
- 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 for 7.17 and 8.x checked on elastic.co/support/eol and endoflife.date on 20 October 2026. Elastic's page no longer lists 7.10 on its own row, so the 11 May 2022 date is from Elastic's earlier table.
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 | 1 Feb 2022 | 15 January 2026 | End of life |
| Elasticsearch 7.10 (this page) | 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 11 May 2022
- Elastic maintenance for 7.10, which ended on 11 May 2022. Every 7.x line is now past end of life; 7.17 ended on 15 January 2026.
- Fixes for later advisories. CVE-2025-37731, a PKI realm impersonation flaw, and CVE-2025-68384, an out-of-memory crash, affect 7.0.0 through 7.17.29 and have no 7.x fix.
- Nothing about the licence. The Apache 2.0 code in 7.10.2 stays Apache 2.0.
What actually breaks in the upgrade
The licence decides the direction
Elasticsearch 7.11 moved to a dual SSPLv1 and Elastic License 2.0 licence, and 8.16 added AGPLv3 as a third option. No 7.x release after 7.10.2 has an open source default licence. Teams that need to stay on Apache 2.0 code move to OpenSearch, which was derived from Elasticsearch 7.10.2.
8.x will not start on old indices
An Elasticsearch 8.0 node will not start with indices created before 7.0, so 6.x indices must be reindexed on 7.x first. Mapping types are gone, and security is on by default from 8.0, which changes every client connection.
On AWS the clock is longer
Amazon OpenSearch Service ends standard support for Elasticsearch 7.10 on 7 November 2027 and offers paid Extended Support to 7 November 2030. Self-managed clusters have no such runway.
CVEs published since the last Elasticsearch 7.x release
These are the CVEs in OSSeva's CVE directory that name the 7.x line, 7.10.2 included, and were published after the last 7.17 release (7.17.29, 24 June 2025). Elastic fixed each in 8.19.x and 9.x only.
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.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Move to OpenSearch | The Apache 2.0 project derived from Elasticsearch 7.10.2. | Scales with index count, clients and the pieces that do not carry over | Engineering time | The natural route when the licence is the reason you stayed on 7.10. |
| Upgrade to Elasticsearch 8.19 or 9.x | Reindex old indices, remove mapping types, configure security. | Scales with index count, clients and plugins | Engineering time plus licence review | Right when Elastic features matter and AGPLv3 or ELv2 works for you. |
| OSSeva patched 7.10.2 | Signed builds of the Apache 2.0 code with backported fixes: Critical 48 hours, High 7 days. | Starts from your current version | Subscription, priced per cluster | Keeps the cluster patched on the same licence while the destination is decided. |
| Stay unpatched | No Elastic fixes since 2022. | None | Zero now | Search clusters often hold the most sensitive data in the estate. |
What OSSeva does for Elasticsearch 7.10
OSSeva patches this line
OSSeva ships patched, signed Elasticsearch 7.10.2 builds from the Apache 2.0 code, with backported CVE fixes, on the Patch, Assure and Operate tiers. OSSeva engineers also run migrations to OpenSearch or to Elasticsearch 8.x.
Elasticsearch extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
When did Elasticsearch 7.10 reach end of life?
On 11 May 2022, under Elastic's end-of-life policy. The last release was 7.10.2 on 14 January 2021.
Is Elasticsearch 7.10.2 open source?
Its OSS distribution is Apache 2.0, and 7.10.2 is the last release with Apache 2.0 as the default licence. The default distribution also bundled x-pack under the Elastic License. From 7.11 the licence is SSPLv1 or Elastic License 2.0.
Is OpenSearch based on Elasticsearch 7.10?
Yes. OpenSearch was derived from Elasticsearch 7.10.2, and OpenSearch Dashboards from Kibana 7.10.2.
Can I keep Elasticsearch 7.10 patched?
Yes. OSSeva ships patched builds of the Apache 2.0 7.10.2 code today.
Get a quote
Still running Elasticsearch 7.10?
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?