CVE-2026-72653: Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service
Affects kibanaSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium · fixed in 9.4.4 : update kibana when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.4.4, 9.3.8, 8.19.19
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.4, 9.3.8 or 8.19.19.
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 apply the official fixes for affected Kibana versions to prevent exploitation. Since this is not a cloud service, remediation requires updating the affected Kibana installations. No additional mitigations are specified.
Description
CVE-2026-72653 is a medium severity vulnerability in Kibana where an authenticated user authorized to manage maintenance windows can submit a specially crafted payload that causes excessive resource allocation. This leads to denial of service as the Kibana process becomes unresponsive and requires manual intervention to recover. The issue affects multiple Kibana versions from 8.12.0 up to but not including 8.19.19, 9.0.0 up to 9.3.8, and 9.4.0 up to 9.4.4. A patch is available to address this vulnerability.