Kibana vulnerabilities: known CVEs & security history
Elastic · Observability · 96 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Kibana release lines — 96 in total. A CVE here doesn't mean your version is affected — check Kibana's current status and the safe version to run.
Known Kibana CVEs
Actively-exploited and most-severe first. Showing the top 80 of 96. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-102406 | high | 8.8 | 0% | 2026 |
| CVE-2025-25018 | high | 8.7 | 0% | 2025 |
| CVE-2025-25009 | high | 8.7 | 0% | 2025 |
| CVE-2026-63137 | high | 8.3 | 0% | 2026 |
| CVE-2025-25017 | high | 8.2 | 0% | 2025 |
| CVE-2026-78583 | high | 8.1 | 0% | 2026 |
| CVE-2026-72665 | high | 8.1 | 0% | 2026 |
| CVE-2026-49091 | high | 8 | 0% | 2026 |
| CVE-2026-72672 | high | 7.7 | 0% | 2026 |
| CVE-2026-72670 | high | 7.7 | 0% | 2026 |
| CVE-2026-42398 | high | 7.7 | 0% | 2026 |
| CVE-2026-4498 | high | 7.7 | 0% | 2026 |
| CVE-2026-33461 | high | 7.7 | 0% | 2026 |
| CVE-2026-72669 | high | 7.6 | 0% | 2026 |
| CVE-2026-78590 | high | 7.3 | 0% | 2026 |
| CVE-2026-78592 | high | 7.3 | 0% | 2026 |
| CVE-2026-72677 | high | 7.3 | 0% | 2026 |
| CVE-2026-72658 | high | 7.3 | 0% | 2026 |
| CVE-2026-72675 | high | 7.1 | 0% | 2026 |
| CVE-2026-72643 | high | 7.1 | 0% | 2026 |
| CVE-2026-72632 | high | 7.1 | 0% | 2026 |
| CVE-2026-72630 | high | 7.1 | 0% | 2026 |
| CVE-2026-72629 | high | 7.1 | 0% | 2026 |
| CVE-2026-56147 | high | 7.1 | 0% | 2026 |
| CVE-2026-72666 | medium | 6.8 | 0% | 2026 |
| CVE-2026-102412 | medium | 6.5 | 0% | 2026 |
| CVE-2026-94400 | medium | 6.5 | 0% | 2026 |
| CVE-2026-78599 | medium | 6.5 | 0% | 2026 |
| CVE-2026-78586 | medium | 6.5 | 0% | 2026 |
| CVE-2026-78608 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72682 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72654 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72652 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72644 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72628 | medium | 6.5 | 0% | 2026 |
| CVE-2026-63138 | medium | 6.5 | 0% | 2026 |
| CVE-2026-33465 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72681 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72680 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72676 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72674 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72667 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72664 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72663 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72661 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72660 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72659 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72653 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72651 | medium | 6.5 | 0% | 2026 |
| CVE-2026-72631 | medium | 6.5 | 0% | 2026 |
| CVE-2026-49089 | medium | 6.5 | 0% | 2026 |
| CVE-2026-63261 | medium | 6.5 | 0% | 2026 |
| CVE-2026-63260 | medium | 6.5 | 0% | 2026 |
| CVE-2026-63139 | medium | 6.5 | 0% | 2026 |
| CVE-2026-42397 | medium | 6.5 | 0% | 2026 |
| CVE-2026-56151 | medium | 6.5 | 0% | 2026 |
| CVE-2026-49087 | medium | 6.5 | 0% | 2026 |
| CVE-2026-49095 | medium | 6.5 | 0% | 2026 |
| CVE-2026-49094 | medium | 6.5 | 0% | 2026 |
| CVE-2026-42400 | medium | 6.5 | 0% | 2026 |
| CVE-2026-42399 | medium | 6.5 | 0% | 2026 |
| CVE-2026-33464 | medium | 6.5 | 0% | 2026 |
| CVE-2026-33459 | medium | 6.5 | 0% | 2026 |
| CVE-2026-78591 | medium | 6.3 | 0% | 2026 |
| CVE-2026-63141 | medium | 6.3 | 0% | 2026 |
| CVE-2026-49093 | medium | 6.3 | 0% | 2026 |
| CVE-2026-33458 | medium | 6.3 | 0% | 2026 |
| CVE-2026-78601 | medium | 5.5 | 0% | 2026 |
| CVE-2026-78598 | medium | 5.4 | 0% | 2026 |
| CVE-2026-72641 | medium | 5.4 | 0% | 2026 |
| CVE-2026-72673 | medium | 5.4 | 0% | 2026 |
| CVE-2026-56146 | medium | 5.4 | 0% | 2026 |
| CVE-2025-37732 | medium | 5.4 | 0% | 2025 |
| CVE-2026-33463 | medium | 5.3 | 0% | 2026 |
| CVE-2026-63142 | medium | 5 | 0% | 2026 |
| CVE-2026-33462 | medium | 4.6 | 0% | 2026 |
| CVE-2026-49088 | medium | 4.4 | 0% | 2026 |
| CVE-2026-102410 | medium | 4.3 | 0% | 2026 |
| CVE-2026-78584 | medium | 4.3 | 0% | 2026 |
| CVE-2026-78603 | medium | 4.3 | 0% | 2026 |
16 older / lower-severity CVEs not shown — see Kibana's full record.
Is my Kibana version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Kibana version → · Monitor Kibana for new CVEs →
Kibana vulnerabilities — frequently asked
How many known vulnerabilities does Kibana have?
IsItPatched tracks 96 CVEs for Kibana. 0 are critical-severity and 24 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Kibana have any actively-exploited vulnerabilities?
None of Kibana's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Kibana vulnerability?
Among tracked issues, CVE-2026-102406 (HIGH, CVSS 8.8) ranks highest — a Authorization bypass weakness.
Is Kibana safe to use?
It depends on the version. The latest supported Kibana release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Kibana security status · Kibana end-of-life · actively-exploited CVEs. Always verify against Elastic's advisories — see our disclaimer.