# CVE-2026-94400: Elastic Kibana denial of service via resource consumption

Source: https://junglewise.ai/threats/cve-2026-94400-uncontrolled-resource-consumption-cwe-400-in-kibana-can-lead  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-26. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-94400 · Severity: medium · CVSS 6.5 · Published 2026-09-26

Kibana, a data visualization and analytics platform, contains a resource consumption vulnerability that allows authenticated attackers to trigger a denial of service. By allocating excessive resources through normal API requests, attackers can exhaust system resources and make Kibana unavailable to legitimate users.

Technologies: [Elastic Kibana](https://junglewise.ai/threats/technologies/kibana). Vendors: [Elastic](https://junglewise.ai/threats/vendors/elastic).

## Quick answers

**Is CVE-2026-94400 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-94400 being exploited in the wild.

**How severe is CVE-2026-94400?** Medium severity, with a CVSS score of 6.5, published 26 September 2026.

**Which products and versions are affected?** Elastic Kibana 8.0.0 to 8.19.21, 9.0.0 to 9.4.6, 9.5.0 to 9.5.2.

**Is there a fix for CVE-2026-94400?** A patch was published on 2026-09-26: Fixed in Kibana 8.19.22, 9.4.7, 9.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-94400 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-94400?** Check whether you run Elastic Kibana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An uncontrolled resource consumption flaw (CWE-400) in Kibana allows authenticated attackers to cause denial of service through excessive allocation. The vulnerability requires login credentials (PR:L) but no user interaction, and is accessible over the network. Exploitation results in availability impact with no confidentiality or integrity compromise.

## Affected products

- Elastic Kibana 8.0.0 to 8.19.21, 9.0.0 to 9.4.6, 9.5.0 to 9.5.2

## Timeline

- 2026-09-25: disclosed: ESA-2026-181 published
- 2026-09-26: patched: Fixed in Kibana 8.19.22, 9.4.7, 9.5.3

## References

- [https://discuss.elastic.co/t/kibana-8-19-22-9-4-7-9-5-3-security-update-esa-2026-181/390685](https://discuss.elastic.co/t/kibana-8-19-22-9-4-7-9-5-3-security-update-esa-2026-181/390685)

## Related threats

- [Elastic Kibana authorization bypass in connector logs](https://junglewise.ai/threats/cve-2026-115295-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana path traversal in Fleet feature](https://junglewise.ai/threats/cve-2026-115294-improper-limitation-of-a-pathname-to-a-restricted-directory-cwe)
- [Elastic Kibana credential disclosure in Observability onboarding](https://junglewise.ai/threats/cve-2026-115293-insertion-of-sensitive-information-into-sent-data-cwe-201-in)
- [Elastic Kibana authorization bypass in Machine Learning](https://junglewise.ai/threats/cve-2026-115292-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana incorrect authorization in Fleet settings](https://junglewise.ai/threats/cve-2026-102412-incorrect-authorization-cwe-863-in-kibana-can-lead-to-sensitive)