Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Network-reachable web interface, low complexity; PR:L because valid credentials are mandatory; A:H for complete process crash; C:N and I:N as no data exposure or modification occurs.
Primary rating from Vendor (elastic).
CVSS VectorVendor: elastic
Lifecycle Timeline
2DescriptionCVE.org
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.
AnalysisAI
Denial of service in Elastic Kibana allows any authenticated low-privilege user to crash the Kibana process by sending a specially crafted oversized HTTP request payload, exhausting Node.js heap memory and making the analytics platform unavailable to all users. Affected branches span Kibana 8.x (through 8.19.18), 9.0.x-9.3.x (through 9.3.7), and 9.4.x (through 9.4.3), with patched releases available per ESA-2026-71. No public exploit code has been identified at time of analysis, and this CVE does not appear in the CISA KEV catalog.
Technical ContextAI
Kibana is Elastic's Node.js-based web frontend for the Elastic Stack, widely used for log analytics, SIEM dashboards, and observability. The root cause is CWE-400 (Uncontrolled Resource Consumption): Kibana fails to enforce bounds on the size of user-supplied request payloads before performing memory allocation proportional to that input. This maps to CAPEC-130 (Excessive Allocation) - the attacker provides a payload large enough to force heap allocations that exhaust the Node.js V8 heap, triggering an out-of-memory crash of the Kibana process. Because Kibana is a single-process service, one successful attack brings down the interface for all concurrent users. Affected CPE covers elastic:kibana versions 8.0.0 through 8.19.18 and 9.0.0 through 9.4.3 as confirmed by EUVD-2026-47588.
RemediationAI
Upgrade to a patched Kibana release: version 8.19.19, 9.3.8, or 9.4.4, per the Elastic security advisory ESA-2026-71 at https://discuss.elastic.co/t/kibana-8-19-19-9-3-8-9-4-4-security-update-esa-2026-71/388574. These fix versions are inferred from the advisory title and EUVD data but have not been independently verified against release artifacts. If immediate patching is not feasible, restrict Kibana access to the minimum necessary set of trusted users, as the PR:L requirement means eliminating untrusted authenticated accounts directly reduces attack surface. Deploying a reverse proxy or API gateway with HTTP request body size limits (e.g., nginx client_max_body_size directive) in front of Kibana can block oversized payloads before they reach the vulnerable process - note this may interfere with legitimate large dashboard imports or bulk operations. Configuring process supervision (systemd with Restart=on-failure or equivalent) reduces sustained downtime from repeated attacks but does not prevent exploitation.
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
Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP
Kibana versions 4.0 to 4.6, 5.0 to 5.6.12, and 6.0 to 6.4.2 contain an error in the way authorization credentials are us
A Prototype pollution vulnerability in Kibana leads to arbitrary code execution via crafted HTTP requests to machine lea
Kibana versions before 6.6.1 contain an arbitrary code execution flaw in the security audit logger. Rated critical sever
Prototype Pollution in Kibana can lead to code injection via unrestricted file upload combined with path traversal. Rate
A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document con
Kibana version 8.7.0 contains an arbitrary code execution flaw. Rated high severity (CVSS 8.8), this vulnerability is re
Kibana versions 8.0.0 through 8.7.0 contain an arbitrary code execution flaw. Rated high severity (CVSS 8.8), this vulne
Kibana versions up to 9.3.0 contains a vulnerability that allows attackers to read arbitrary files from the Kibana serve
Same weakness CWE-400 – Uncontrolled Resource Consumption
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-47588
GHSA-qcp3-347v-7f6g