← Search results
CVE-LINKED INVENTORY192 SECURITY RECORDS
Elastic
kibana
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Kibana. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2021-22150 | 22 Nov 2023 | 7.10.2 < 7.14.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-31422 | 26 Oct 2023 | 8.10.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-31415 | 4 May 2023 | version 8.7.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-31414 | 4 May 2023 | versions 8.0.0 through 8.7.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-38779 | 21 Feb 2023 | Kibana Versions 7.0.0 through 7.17.8 and 8.0.0 through 8.6.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-38778 | 8 Feb 2023 | Versions 7.0.0 through 7.17.8 and 8.0.0 through 8.6.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-37936 | 18 Nov 2022 | versions before 7.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-22141 | 18 Nov 2022 | All versions of Kibana before 7.13.0 and 6.8.16. | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23713 | 6 Jul 2022 | Versions 7.0.0 through 7.17.4 and 8.0.0 through 8.2.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23711 | 21 Apr 2022 | Versions 7.2.1 through 7.17.2 & 8.0.0 through 8.1.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23710 | 3 Mar 2022 | For self-managed deployments the issue impacts versions 7.15.0, 7.15.1, and 7.15.2 For Elastic Cloud Services the issue impacts versions 7.15.0 through 7.17.0, and 8.0.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23709 | 3 Mar 2022 | Versions 7.7.0 through 7.17.0, and 8.0.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23707 | 11 Feb 2022 | 7.5.1 through 7.16.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-37939 | 18 Nov 2021 | All versions from 7.8.0 through 7.15.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-37938 | 18 Nov 2021 | All versions from 7.9.0 through 7.15.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-22139 | 13 May 2021 | before 7.12.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-22136 | 13 May 2021 | before 7.12.0 and 6.8.15 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-7017 | 27 Jul 2020 | before 6.8.11 and 7.8.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-7016 | 27 Jul 2020 | before 6.8.11 and 7.8.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-7015 | 3 Jun 2020 | before 6.8.9 and 7.7.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-7013 | 3 Jun 2020 | before 6.8.9 and 7.7.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-7012 | 3 Jun 2020 | 6.7.0 to 6.8.8 and 7.0.0 to 7.6.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-7621 | 18 Dec 2019 | before 6.8.6 and 7.5.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-7616 | 30 Jul 2019 | before 7.2.1 and 6.8.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-7610 | 25 Mar 2019 | before 6.6.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-7608 | 25 Mar 2019 | before 5.6.15 and 6.6.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-7609 | 25 Mar 2019 | Kibana: before 5.6.15 and 6.6.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-17246 | 20 Dec 2018 | before 6.4.3 and 5.6.13 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-17245 | 20 Dec 2018 | 4.0 to 4.6, 5.0 to 5.6.12, and 6.0 to 6.4.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-3830 | 19 Sep 2018 | after 5.3.0, before 5.6.12 and 6.4.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-3821 | 30 Mar 2018 | after 5.1.1 and before 5.6.7 and 6.1.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-3820 | 30 Mar 2018 | after 6.1.0 and before 6.1.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-3819 | 30 Mar 2018 | All versions before 6.1.3 and 5.6.7 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-3818 | 30 Mar 2018 | 5.1.1 to 6.1.2 and 5.6.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-11482 | 8 Dec 2017 | before 6.0.1 and 5.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-11481 | 8 Dec 2017 | before 6.0.1 and 5.6.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-8452 | 16 Jun 2017 | before 5.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-10366 | 16 Jun 2017 | 4.3 to 4.6.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-10365 | 16 Jun 2017 | before 5.0.1 and 4.6.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2015-9056 | 16 Jun 2017 | before 4.1.3 and 4.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-8440 | 5 Jun 2017 | 5.3.0 to 5.3.3; 5.4.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-8439 | 5 Jun 2017 | 5.4.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.