CVE-2026-72660: Kibana Leading to Denial of Service · Uncaught Exception
Affects kibanaSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium · fixed in 9.4.5 : update kibana when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.4.5, 9.3.8, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade kibana to 9.4.5, 9.3.8 or 8.19.20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikibanapkg:bitnami/kibanaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for this vulnerability. Users should upgrade Kibana to versions 8.19.20 or later, 9.3.8 or later, and 9.4.5 or later as applicable. Since this is not a cloud service, administrators must apply the update manually to remediate the issue.
Description
CVE-2026-72660 is a vulnerability in Kibana where an uncaught exception caused by improper input validation can lead to a denial of service. An authenticated user with low privileges can supply specially crafted data that triggers an internal error, causing the Kibana process to terminate. This results in service unavailability until the system is restarted. The issue affects multiple Kibana versions prior to specific fixed releases. No known exploits are reported in the wild, and a patch is available.