CISA list

Kibana versions

Kibana: update to 9.5.6, 9.4.9 or 8.19.25. 9.3, 9.2, 9.1 and 9.0 and older no longer get fixes.

Data: .

Which Kibana 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 Kibana branch to run
BranchStatusNewest safe releaseUpgrade to
9.530 CVE records that this page readsFixes, no end date announced9.5.69.5.6 (this branch)
9.485 CVE records that this page readsFixes, no end date announced9.4.99.4.9 (this branch)
9.344 CVE records that this page readsEnded on 4 August 2026None, the branch has ended9.4.9 (move to 9.4)
9.222 CVE records that this page readsEnded on 5 May 2026None, the branch has ended9.4.9 (move to 9.4)
9.117 CVE records that this page readsEnded on 3 February 2026None, the branch has ended9.4.9 (move to 9.4)
8.1992 CVE records that this page readsFixes until 15 July 20278.19.258.19.25 (this branch)
9.08 CVE records that this page readsEnded on 23 October 2025None, the branch has ended8.19.25 (move to 8.19)
8.187 CVE records that this page readsEnded on 21 October 2025None, the branch has ended8.19.25 (move to 8.19)
8.174 CVE records that this page readsEnded on 12 August 2025None, the branch has ended8.19.25 (move to 8.19)
8.162 CVE records that this page readsEnded on 15 April 2025None, the branch has ended8.19.25 (move to 8.19)
8.153 CVE records that this page readsEnded on 12 December 2024None, the branch has ended8.19.25 (move to 8.19)
8.14Ended on 12 November 2024None, the branch has ended8.19.25 (move to 8.19)
724 CVE records that this page readsEnded on 15 January 2026None, the branch has ended8.19.25 (move to 8.19)
6Ended on 10 February 2022None, the branch has ended8.19.25 (move to 8.19)

Exploited, or likely to be

CVE records for Kibana 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 3 records shown names one. None of the 3 records shown is placed on a branch, so no release is shown for them; the note under each says why.

Exploited, or likely to be
RecordSigns of exploitationFixed in
CVE-2019-7609Arbitrary Code Execution9.8 Critical · published 25 March 2019On CISA's list
Metasploit module
EPSS 0.50 or more
This page does not place it on a branch: the record's versions are in a form it does not read.
CVE-2020-7012Kibana versions 6.7.0 to 6.8.8 and 7.0.0 to 7.6.2 contain a prototype pollution flaw in the Upgrade Assistant. An authenticated attacker with privileges to write to the Kibana index could insert…published 3 June 2020Metasploit moduleThis page does not place it on a branch: the record's versions are in a form it does not read.
CVE-2018-17246Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. An attacker with access to the Kibana Console API could send a request that will attempt to…published 20 December 2018EPSS 0.50 or moreThis page does not place it on a branch: the record's versions are in a form it does not read.

CISA's list for the vendor

The entries CISA lists under the vendor names it uses for Kibana, 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 196 CVE records that Elastic's CVE Numbering Authority published and that name Kibana. The fixes are from the 143 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.

53 records are not placed on a branch, so no branch or release row counts them: 37 give their versions in a form this page does not read exactly; 11 have a range that ends in a release the lifecycle data has no branch for; 3 have a range with no start or no end; 2 name a release the lifecycle data has no branch for. They are CVE-2015-9056, CVE-2016-10365, CVE-2016-10366, CVE-2017-8439, CVE-2017-8440, CVE-2017-8452, CVE-2017-11481, CVE-2017-11482, CVE-2018-3818 and CVE-2018-3819 and 43 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)