Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-accessible IDOR requiring a valid authenticated session (PR:L); impact is read-only partial confidentiality loss scoped to scheduled query results, no integrity or availability effect.
Primary rating from Vendor (elastic).
CVSS VectorVendor: elastic
Lifecycle Timeline
2DescriptionCVE.org
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
AnalysisAI
Kibana's multi-tenancy Spaces model can be bypassed through an Insecure Direct Object Reference (IDOR) vulnerability, allowing authenticated users to read scheduled query results belonging to Spaces they are not authorized to access. Affected versions span Kibana 9.4.0 through 9.4.3, with the fix delivered in 9.4.4. The CVSS vector (PR:L, C:L) confirms the impact is limited to low-privilege authenticated access resulting in partial confidentiality loss - no integrity or availability impact is involved. No public exploit code exists and no CISA KEV listing has been identified at time of analysis.
Technical ContextAI
Kibana Spaces is an Elastic-native multi-tenancy feature that logically isolates dashboards, saved objects, and query data between organizational units within a single Kibana instance. CWE-639 (Authorization Bypass Through User-Controlled Key) describes an Insecure Direct Object Reference pattern where the application uses attacker-controllable identifiers - in this case, identifiers referencing scheduled query result objects - to fetch backend resources without adequately verifying that the requester holds access rights to the target Space. Because the identifier is trusted at the API layer without re-validating Space membership, a user legitimately authenticated to one Space can reference and retrieve data stored in a different, restricted Space. The affected surface is scoped to scheduled query results specifically, not the broader Kibana object model. Elastic reported this through their own security disclosure address (security@elastic.co), tracked externally as ENISA EUVD-2026-47585.
RemediationAI
Upgrade Kibana to version 9.4.4 or later, which contains the vendor-released fix per ESA-2026-70 (https://discuss.elastic.co/t/kibana-9-4-4-security-update-esa-2026-70/388573). This is the primary and recommended remediation path. If an immediate upgrade is operationally blocked, consider restricting access to the Kibana API endpoints that serve scheduled query results to trusted network segments or authenticated service accounts only, using Elastic's built-in role-based access control to reduce the user population that can issue API requests. Additionally, auditing Kibana role assignments to minimize the number of accounts granted any Space access reduces the potential attacker pool. Note that these workarounds do not eliminate the underlying IDOR condition and should be treated as temporary compensating controls only. No patch version other than 9.4.4 is confirmed in the available data.
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 technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-47585
GHSA-vv4j-vm47-33w3