Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
3DescriptionCVE.org
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user with access to the automatic import feature can submit specially crafted requests with excessively large input values. When multiple such requests are sent concurrently, the backend services become unstable, resulting in service disruption and deployment unavailability for all users.
AnalysisAI
Denial of service in Kibana's automatic import feature allows authenticated users to trigger uncontrolled resource consumption by submitting specially crafted requests with excessively large input values. When multiple such requests are sent concurrently, backend services become unstable, resulting in service disruption across all users. CVSS 6.5 (medium severity) reflects the authenticated attack requirement and high availability impact without confidentiality or integrity compromise.
Technical ContextAI
The vulnerability exists in Kibana's automatic import feature, which fails to properly validate and limit resource consumption when processing user-supplied input. The root cause is CWE-400 (Uncontrolled Resource Consumption), where the backend does not enforce adequate bounds checking or rate limiting on input size or concurrent request processing. Kibana (cpe:2.3:a:elastic:kibana) is Elastic's analytics and visualization platform built on the Elastic Stack; the automatic import functionality enables bulk data ingest operations. When multiple oversized requests reach the backend simultaneously, they exhaust system resources (CPU, memory, or connection pools), triggering cascading service degradation. This is a classic CAPEC-130 (Excessive Allocation) attack pattern exploiting a lack of resource quotas or queue depth enforcement.
RemediationAI
Upgrade to Kibana 8.19.14 or later for the 8.x branch, or upgrade to Kibana 9.2.8 or later for the 9.x branch (9.3.x users should upgrade to 9.3.3 or later). Consult the Elastic security advisory at https://discuss.elastic.co/t/kibana-8-19-14-9-2-8-9-3-3-security-update-esa-2026-26/385814 for detailed upgrade guidance and version mapping. As an interim workaround pending patching, restrict access to the automatic import feature via role-based access controls (RBAC), limiting the feature to trusted administrators only, or disable the feature entirely if not required. Additionally, implement network-level or reverse-proxy rate limiting and request size caps on the import endpoint to prevent resource exhaustion from large or concurrent requests.
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the s
The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execut
Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction wi
Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unsp
Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, a
Kibana versions before 5.6.15 and 6.6.1 contain an arbitrary code execution flaw in the Timelion visualizer. Rated criti
Kibana versions 6.7.0 to 6.8.8 and 7.0.0 to 7.6.2 contain a prototype pollution flaw in the Upgrade Assistant. Rated hig
Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. Rated critical s
opensearch-ruby is a community-driven, open source fork of elasticsearch-ruby. Rated high severity (CVSS 8.8), this vuln
Icinga is a monitoring system which checks the availability of network resources, notifies users of outages, and generat
A symbolic link following vulnerability in Buildkite Elastic CI for AWS versions prior to 6.7.1 and 5.22.5 allows the bu
All versions of Elastic Cloud Enterprise has the Elasticsearch “anonymous” user enabled by default in deployed clusters.
Same weakness CWE-400 – Uncontrolled Resource Consumption
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-20521
GHSA-p635-f626-pv4p