// Elasticsearch 7.17 after end of life

Elasticsearch 7.17 after end of life: stay patched, move to 8.x, or OpenSearch

Elasticsearch EOL for 7.17 has passed: Elastic ended maintenance on 15 April 2025 and support on 15 January 2026, and the last release is 7.17.29. You can upgrade to 8.19 or 9.x, move to OpenSearch, or keep 7.17 and 7.10.2 patched with signed OSSeva builds while you choose. Enter your work email and the Elasticsearch version you run, and an engineer replies within 1 business day.

Patched builds
Elasticsearch 7.17 and 7.10.2, signed, as drop-in packages and images
Migration
Planning and execution for Elasticsearch 8.x or OpenSearch, per cluster
Also supported
Elasticsearch 8.x, 9.x and OpenSearch 2 and 3
Critical CVEs (CVSS 9.0 or higher)
Patched within 48 hours
High-severity CVEs
Patched within 7 days
Support hours
Assure includes 24/7 reactive support and the CVE attestation with VEX; Operate adds a 15-minute P1 response

Dates checked on 20 October 2026 against elastic.co/support/eol and endoflife.date, which agree on 7.17 and 8.x. Amazon OpenSearch Service dates are from AWS's announcement of 7 August 2026.

Elasticsearch 7.177.10.28.199.xOpenSearch 1 to 3Self-managed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Elasticsearch versions and end-of-life dates

Elasticsearch EOL for 7.17 passed in two steps: Elastic ended maintenance (bug-fix and security releases) on 15 April 2025 and ended support on 15 January 2026. The last 7.17 release is 7.17.29, from 24 June 2025. 8.x loses maintenance on 15 January 2027 and support on 15 July 2027. Dates checked 20 October 2026 on elastic.co and endoflife.date, which agree.

LineReleasedElastic maintenance endsElastic support endsLatest releaseStatus
Elasticsearch 9.x9.0 on 15 Apr 2025Later of 15 Oct 2027 and 18 months after 10.0Six months after maintenance9.5.6 (2 Nov 2026)Supported upstream; only the newest minors get releases
Elasticsearch 8.1929 Jul 202515 Jan 202715 Jul 20278.19.24 (2 Nov 2026)Supported until 15 Jan 2027; 8.0 to 8.18 have ended
Elasticsearch 7.171 Feb 202215 Apr 202515 Jan 20267.17.29 (24 Jun 2025)Ended: OSSeva patched builds
Elasticsearch 7.10.214 Jan 2021Ended with 7.xEnded with 7.x7.10.2Last Apache 2.0 release: OSSeva patched builds
OpenSearch 3.x6 May 2025No end date setNo end date set3.9.0 (29 Sep 2026)Supported upstream
OpenSearch 2.x26 May 2022No end date setNo end date set2.19.6 (6 Jul 2026)Still releasing upstream
OpenSearch 1.x12 Jul 20216 May 20256 May 20251.3.20Ended

Sources: elastic.co/support/eol and endoflife.date/elasticsearch for Elastic; endoflife.date/opensearch and opensearch.org/releases for OpenSearch. Elastic's table lists 7.17 as the only supported-then-ended 7.x line, so 7.10.2 is shown against the 7.x major. Elastic's 9.x terms are the later of 30 months from GA and 18 months after the next major.

Every Elasticsearch line on one chart →

Advisories published since the last Elasticsearch 7.17 release

The last 7.17 release shipped on 24 June 2025. The CVE directory lists four Elasticsearch advisories published after that date whose records cover the 7.x line, scored from 5.7 up to 7.4, and none is scored 9.0 or higher. Elastic fixed each one in 8.19.x and 9.x only, so no 7.17 build carries a fix. Two further advisories scored 8.8 in August and September 2026 (CVE-2026-72642 and CVE-2026-72649) name only 8.x and 9.x; that means 7.x was not assessed, which is not a finding that it is safe. Deciding which of them reach your 7.17 or 7.10.2 cluster and configuration is the CVE attestation OSSeva writes.

Name 7.x and have no 7.x fix (4 in the directory)

CVEPublishedCVSSAffected range (NVD)Fixed upstream in
CVE-2025-377272025-10-105.77.0.0 to 7.17.29; 8.0.0 to 8.18.7; 8.19.0 to 8.19.4; 9.0.0 to 9.0.7; 9.1.0 to 9.1.48.18.8; 8.19.5; 9.0.8; 9.1.5
CVE-2025-377312025-12-157.4All 7.x; 8.0.0 to 8.19.7; 9.0.0 to 9.1.7; 9.2.0 to 9.2.18.19.8; 9.1.8; 9.2.2
CVE-2025-683842025-12-186.5All 7.x; 8.0.0 to 8.19.8; 9.0.0 to 9.1.8; 9.2.0 to 9.2.28.19.9; 9.1.9; 9.2.3
CVE-2026-726832026-08-136.55.0.0 to 8.19.18; 9.3.0 to 9.3.7; 9.4.0 to 9.4.38.19.19; 9.3.8; 9.4.4

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 Elasticsearch advisory. Affected ranges are as the MITRE record publishes them: CVE-2025-37727 names 7.0.0 to 7.17.29, CVE-2025-37731 and CVE-2025-68384 name 7.0.0 to 7.17.29, and CVE-2026-72683 names 5.0.0 to 8.19.18. Fixed in: 8.19.5 and 9.0.8 or later (CVE-2025-37727), 8.19.8 and 9.1.8 or later (CVE-2025-37731), 8.19.9 and 9.1.9 or later (CVE-2025-68384), 8.19.19 and 9.3.8 or later (CVE-2026-72683).

Elasticsearch CVEs by version, 7.x to 9.x →

What blocks a move from Elasticsearch 7.17 to 8.x or OpenSearch

Both routes start from the same inventory: which indices, mappings, plugins, pipelines and clients the 7.17 cluster depends on. The table lists the 7.17 features that most often decide the route, with what each destination does about them.

On your 7.17 clusterMove to Elasticsearch 8.xMove to OpenSearch
Indices created in 6.x or earlierNot supported in 8.x, closed ones included. Reindex them on 7.17 first.OpenSearch's Migration Assistant takes Elasticsearch 5.x to 7.x sources straight to OpenSearch 1, 2 and 3 by snapshot backfill.
Mapping types and typed endpointsRemoved in 8.0, with their endpoints. Clients need typeless calls; a compatibility header reroutes typed requests.Metadata migration has a type-mapping transform step; multi-type mappings need a decision per index.
Security configurationEach xpack.security SSL setting needs its enabled flag and a certificate and key, and removed settings stop the node starting.Not migrated automatically; configure security on the target cluster.
ILM policies, ingest pipelines, data streamsCarried by the upgrade; ILM policies get stricter validation and the freeze action becomes a no-op.Not migrated automatically; recreate them on the target.
Third-party pluginsPlugins are built for one exact Elasticsearch version and must be rebuilt for 8.x. Plugins can no longer intercept REST requests.Elasticsearch plugins do not carry over; each needs an OpenSearch equivalent or a rebuild.
Official Elastic clientsMove to the 8.x clients. Date formats change from Joda to java-time.Elastic's Python client has refused non-Elasticsearch servers since 7.14.0, so clients move to OpenSearch client libraries.
Kibana dashboardsUpgrade Kibana with the cluster.Dashboards objects are exported and imported through the OpenSearch Dashboards UI.
LicenceSSPLv1 or Elastic License 2.0, and AGPLv3 from 8.16.Apache 2.0.

Sources: Elastic, Migrating to 8.0 (Elasticsearch Guide 8.19); OpenSearch documentation, Migration Assistant: supported migration paths and component support; Elastic Python client 7.17 release notes (7.14.0, 2 August 2021). Checked 20 October 2026.

Elasticsearch 7.17 upgrade options: 8.19, 9.x or OpenSearch →Elasticsearch vs OpenSearch: licensing, support and AWS →

Why Elasticsearch 7 clusters are stuck

Search clusters outlive their upgrade plans because every path forward touches data, clients or licence.

8.x cannot read 6.x indices

Indices created in Elasticsearch 6.x or earlier must be reindexed before a cluster can run 8.x. For large clusters that costs I/O time and a temporary increase in storage.

Clients and security change together

8.x removes mapping types and the API endpoints that used them, and enables security by default. Every application that talks to the cluster needs changes and testing.

7.10.2 is a licence decision

From 7.11, Elasticsearch moved to SSPL and the Elastic License, and 7.x never received the later AGPL option. Products that embed Elasticsearch, and teams with licence policies, stayed on 7.10.2 or moved to OpenSearch, and Elastic patches neither 7.x line now.

The dates that matter

  1. 2021-01-14

    Elasticsearch 7.10.2 released, the last version available under Apache 2.0.

  2. 2025-04-15

    Elastic ends maintenance for 7.17: no more bug-fix or security releases planned.

  3. 2025-06-24

    Elasticsearch 7.17.29, the last 7.x release.

  4. 2026-01-15

    Elasticsearch 7.17 end of support.

  5. 2026-11-07

    Amazon OpenSearch Service raises the Extended Support charge on Elasticsearch 1.5 to 7.8.

  6. 2027-01-15

    Elastic ends maintenance for Elasticsearch 8.x; support ends on 15 July 2027.

  7. 2027-11-07

    Amazon OpenSearch Service ends standard support for Elasticsearch 7.10; Extended Support runs to 7 November 2030.

What OSSeva delivers

1

Patched Elasticsearch 7.x

Backported security fixes for 7.10.2 and 7.17, including the bundled JDK and libraries, as packages and images, with a written CVE attestation for your configuration.

7.10.27.17Bundled JDKVEX
2

Migration planning

Index inventory, reindex sizing, client and plugin audit, and a decision between 8.x and OpenSearch per cluster.

ReindexClients8.x or OpenSearch
3

Executed migrations, then support

Reindex or remote-reindex runs, dual-write cutovers and rollback plans, carried out by engineers who run search clusters. OSSeva supports the OpenSearch cluster you land on.

CutoverDual writeRollbackOpenSearch

Move to Elasticsearch 8.x

Elastic's own path is 7.17 to 8.19, then 9.x. A 7.17 cluster can go to 8.x without a reindex only if every index was created in 7.x; older indices are reindexed on 7.17 first. Land on 8.19, not an earlier 8.x minor: Elastic maintains 8.x only until 15 January 2027, so 8.19 is a stop on the way to 9.x rather than a resting place.

What sets the scope is the number and size of indices, the count of applications and client libraries that talk to the cluster, the plugins and ingest pipelines in use, and the downtime window your business allows. The table above lists the 7.17 features that most often decide the route.

OpenSearch extended support and migration

OpenSearch is the Apache 2.0 fork of Elasticsearch 7.10.2. OpenSearch's Migration Assistant moves Elasticsearch 5.x to 7.x sources, 7.17 included, directly to OpenSearch 1, 2 or 3 by snapshot backfill, optionally with live traffic capture and replay. It does not move security configuration, ILM policies, ingest pipelines, data streams or Dashboards objects, so those are rebuilt on the target.

OSSeva plans and runs that migration and then supports OpenSearch 2 and 3 on the Patch, Assure and Operate tiers. If you would rather not choose yet, patched 7.17 builds keep the old cluster covered until you do.

Stay on 7.17 with patched builds

Patched builds keep the index format, the configuration and the client contract of the version you run, so a cluster swaps to them in place. Fixes ship within 48 hours for Critical CVEs and 7 days for High, as signed packages or images from your own repository, and each advisory gets a written assessment against your configuration: fixed, not present, or not reachable.

Support is a subscription priced per cluster. The cost calculator compares it with the other routes.

Which vendors provide Elasticsearch 7.17 security patches after end of life?

OptionWhat you getTrade-off
Upgrade to Elasticsearch 8.19 or 9.xSupported Elastic releasesReindexing, client changes and Elastic's current licence terms. 8.x maintenance ends on 15 January 2027.
Migrate to OpenSearchAn Apache-2.0 fork of 7.10.2, supported by OSSeva after the moveA migration of clusters, clients, tooling and the pieces the migration tooling does not carry over.
Amazon OpenSearch Service Extended SupportPatched Elasticsearch 7.10 inside AWS until 7 November 2030A per-normalised-instance-hour charge on top of the instance, and only inside AWS.
OSSeva patched buildsPatched self-managed 7.10.2 and 7.17, and planning for the moveA subscription while you migrate, priced per cluster.
Stay unpatchedNothingAdvisories that name 7.x stay open on the system that holds your searchable data.

Dates checked 20 October 2026. Elastic dates from elastic.co/support/eol and endoflife.date; OpenSearch dates from endoflife.date and opensearch.org; migration limits from Elastic's Migrating to 8.0 guide and the OpenSearch Migration Assistant documentation; CVE details from the CVE directory and the MITRE records; AWS dates from the Amazon OpenSearch Service announcement of 7 August 2026.

Questions

Frequently asked questions

Book a 15-minute call

When is Elasticsearch 7.17 end of life?

Elastic ended maintenance for 7.17 on 15 April 2025 and support on 15 January 2026. The last release is 7.17.29, from 24 June 2025. Dates checked on elastic.co and endoflife.date on 20 October 2026.

When does Elasticsearch 8 reach end of life?

Elastic ends maintenance for 8.x on 15 January 2027 and support on 15 July 2027. Only 8.19 is still maintained among the 8.x lines.

Why are companies moving away from Elasticsearch?

Mostly licence and upgrade cost. From 7.11 Elasticsearch moved off Apache 2.0 to SSPL and the Elastic License, and an 8.x upgrade means reindexing old indices, changing clients and turning on security. Teams with licence policies, or products that embed Elasticsearch, move to OpenSearch instead.

Are OpenSearch and Elasticsearch the same?

No. OpenSearch is a fork of Elasticsearch 7.10.2 under Apache 2.0 and has developed separately since. Elasticsearch 7.x data and queries migrate to it, but plugins, security configuration, pipelines and client libraries do not carry over unchanged.

Is Elasticsearch 7.10.2 the last open source version?

It is the last release available under Apache 2.0, through its OSS distribution. From 7.11 Elasticsearch used SSPL and the Elastic License; Elastic added an AGPL option from 8.16. OpenSearch was forked from 7.10.2 to keep Apache 2.0.

Are there Elasticsearch 7.17 vulnerabilities without a fix?

Yes. The table above lists four in the CVE directory, published since the last 7.17 release, that name all of 7.x as affected. Elastic fixed them in 8.19.x and 9.x only and ships no further 7.x releases.

Can I upgrade Elasticsearch 7 to 8 without reindexing?

Only if every index was created in 7.x. Indices from 6.x or earlier must be reindexed first.

Who provides security patches for Elasticsearch 7.10.2?

Elastic does not patch 7.10.2. AWS patches it inside OpenSearch Service under paid Extended Support. For self-managed clusters, OSSeva provides patched builds.

Get a quote

Keep 7.x patched while you decide where it goes.

Send your work email and the Elasticsearch version you run. An engineer replies within 1 business day; support is priced per cluster.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call