CISA list

Elasticsearch versions

Elasticsearch: update to 9.5.6 or 8.19.25. 9.4 has no safe release yet. 9.3, 9.2, 9.1 and 9.0 and older no longer get fixes.

Data: .

Which Elasticsearch branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records we cannot place on a branch are counted at the end of the page.

Which Elasticsearch branch to run
BranchStatusNewest safe releaseUpgrade to
9.528 CVE records that this page readsFixes, no end date announced9.5.69.5.6 (this branch)
9.443 CVE records that this page readsFixes, no end date announcedNone yet9.5.6 (move to 9.5)
9.314 CVE records that this page readsEnded on 4 August 2026None, the branch has ended9.5.6 (move to 9.5)
9.26 CVE records that this page readsEnded on 5 May 2026None, the branch has ended9.5.6 (move to 9.5)
9.14 CVE records that this page readsEnded on 3 February 2026None, the branch has ended9.5.6 (move to 9.5)
8.1947 CVE records that this page readsFixes until 15 July 20278.19.258.19.25 (this branch)
9.01 CVE record that this page readsEnded on 23 October 2025None, the branch has ended8.19.25 (move to 8.19)
8.181 CVE record that this page readsEnded on 21 October 2025None, the branch has ended8.19.25 (move to 8.19)
8.171 CVE record that this page readsEnded on 12 August 2025None, the branch has ended8.19.25 (move to 8.19)
8.161 CVE record that this page readsEnded on 15 April 2025None, the branch has ended8.19.25 (move to 8.19)
79 CVE records that this page readsEnded on 15 January 2026None, the branch has ended8.19.25 (move to 8.19)
62 CVE records that this page readsEnded on 10 February 2022None, the branch has ended8.19.25 (move to 8.19)

Exploited, or likely to be

CVE records for Elasticsearch that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the releases that fix each where the record names them. None of the 4 records shown names one. 3 of the 4 records shown are not placed on a branch, so no release is shown for them; they are listed here, each with a note that says why.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2015-1427Groovy Scripting Engine Remote Code Execution9.8 Critical · published 17 February 2015On CISA's list
Metasploit module
Exploit-DB entry
EPSS 0.50 or more
No record that we read gives its versions, so this page does not place it on a branch.
CVE-2014-3120Remote Code Execution8.1 High · published 28 July 2014On CISA's list
Metasploit module
Exploit-DB entry
EPSS 0.50 or more
No record that we read gives its versions, so this page does not place it on a branch.
CVE-2021-22145A memory disclosure vulnerability was identified in Elasticsearch 7.10.0 to 7.13.3 error reporting. A user with the ability to submit arbitrary queries to Elasticsearch could submit a malformed…published 21 July 2021Metasploit module
Exploit-DB entry
EPSS 0.50 or more
The record names no fixed release for 7.
CVE-2023-31419Elasticsearch StackOverflow vulnerability6.5 Medium · published 26 October 2023EPSS 0.50 or moreThis page does not place it on a branch: its range ends in a release the lifecycle data has no branch for.

Records that reach a branch that still gets fixes

These records give a range that runs across a branch that still gets fixes. As the record states it, the range holds releases of that branch, so this page does not place it on a branch.

Records that reach a branch that still gets fixes
RecordSigns of exploitationFixed in
CVE-2026-72639Memory Allocation with Excessive Size Value in Elasticsearch Highlighting Leading to Denial of Service6.5 Medium · published 13 August 2026NoneIts range runs from 9.3.0 up to and including 9.5.0 and reaches 9.4, which still gets fixes. This page does not place it on a branch. The range holds 9.4.9 of 9.4, so no release of the branch is called safe while it is open.

CISA's list for the vendor

The entries CISA lists under the vendor names it uses for Elasticsearch, each with its patch-first group.

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 91 CVE records that Elastic's CVE Numbering Authority published and that name Elasticsearch. The fixes are from the 57 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended.

Some records give a range that starts in an older release and ends in a newer branch. The lifecycle data does not list a branch for every release a range starts at, and such a release gets no row here. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the branches the lifecycle data lists between its start and its end. Only a range that runs across branches that have all ended is placed. A range that ends in a release the lifecycle data has no branch for is not placed either. A range that reaches a branch that still gets fixes is not placed either: the record with such a range is under "Records that reach a branch that still gets fixes", and no release is called safe that one of them holds.

34 records are not placed on a branch, so no branch or release row counts them: 17 give their versions in a form this page does not read exactly; 14 have a range that ends in a release the lifecycle data has no branch for; 1 has a range that reaches a branch that still gets fixes; 2 have a range with no start or no end. They are CVE-2018-3827, CVE-2018-3831, CVE-2018-17247, CVE-2019-7611, CVE-2019-7614, CVE-2019-7619, CVE-2020-7009, CVE-2020-7014, CVE-2020-7019 and CVE-2020-7020 and 24 others.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)