CVE-2026-42400
Uncontrolled Resource Consumption in Kibana via Excessive Allocation
Publication date: 2026-05-28
Last updated on: 2026-05-28
Assigner: Elastic
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| elastic | kibana | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-400 | The product does not properly control the allocation and maintenance of a limited resource. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual spikes in memory and CPU resource utilization on the Kibana instance.
Additionally, checking access logs for large compressed request payloads can help identify potential exploitation attempts.
Indicators of compromise include unexpected crashes or the Kibana instance becoming unresponsive.
- Use system monitoring tools like 'top' or 'htop' on the Kibana server to observe CPU and memory usage.
- Inspect Kibana access logs for unusually large compressed requests, for example using: grep -i --binary-files=text 'Content-Encoding: gzip' /path/to/kibana/logs/access.log | awk '{print length, $0}' | sort -nr | head
- Use network monitoring tools like tcpdump or Wireshark to capture and analyze compressed HTTP requests to Kibana.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
This vulnerability is an Uncontrolled Resource Consumption issue (CWE-400) in Kibana. It allows an authenticated user to send a specially crafted compressed request payload that is processed before authorization checks. This causes excessive memory and CPU usage, which can make the Kibana instance unresponsive or cause it to crash.
How can this vulnerability impact me? :
The impact of this vulnerability is a denial of service condition. Because the specially crafted request consumes excessive system resources, it can cause the Kibana service to become unresponsive or crash, disrupting availability.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade Kibana to a fixed version where the vulnerability is resolved.
- Upgrade to Kibana version 8.19.16 or later if using the 8.x series.
- Upgrade to Kibana version 9.3.5 or later if using the 9.3.x series.
- Upgrade to Kibana version 9.4.2 or later if using the 9.4.x series.
No workarounds exist for users unable to upgrade, so applying the update is critical to prevent denial of service.