Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged Kibana user in shared space
-
DeliveryEnumerate other users' draft Timeline object IDs
-
ExploitBypass per-user ACL via user-controlled key
-
ExecutionRead/modify/delete victims' Timeline drafts
-
ImpactUnauthorized disclosure or data tampering
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires an authenticated Kibana user account that has been granted the Timeline feature privilege within a Kibana space (PR:L). Read/enumeration/disclosure of other users' draft Timeline objects requires only Timeline read access; modification and deletion additionally require the Timeline write privilege. Exploitation is limited to draft Timeline objects belonging to other users in the SAME Kibana space, so the flaw is only meaningful in multi-user shared-space deployments where Timeline privileges are granted to more than one principal - a single-user space or environments that do not use the Timeline feature are not exposed. No user interaction from the victim is needed. |
| Impact | This is a genuine but moderate-severity issue, best characterized as a same-space, cross-user authorization bypass (CWE-639 / IDOR) rather than a critical break. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, base 6.3) is internally consistent with the description: exploitation is network-reachable and low-complexity, but requires an authenticated Kibana user who has already been granted the Timeline feature privilege in a space (PR:L), and impact is limited to draft Timeline objects belonging to other users in that same space (Low confidentiality, integrity, and availability). No EPSS score, CISA KEV entry, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are aligned rather than conflicting: a high-fidelity vendor advisory (Elastic ESA-2026-103) with a moderate CVSS and no exploitation indicators points to a real but non-urgent patch-management priority - an insider/multi-tenant data-integrity concern, not an internet-facing pre-auth RCE. The main caveats are that PR:L is only meaningful where multiple users share a Kibana space and Timeline privileges are broadly granted, and that write/modify/delete impact requires the additional Timeline write privilege (read-only users can still enumerate and disclose). |
| Exploit ScenarioDerived | An authenticated Kibana user who has been granted the Timeline feature privilege within a shared space enumerates and reads draft Timeline objects created by other analysts in that same space, disclosing investigation data they should not see. If that same user also holds the Timeline write privilege, they can modify or delete other users' draft Timelines, tampering with or destroying colleagues' work. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Cross-user authorization bypass in Elastic Kibana lets an authenticated user who holds the Timeline feature privilege in a Kibana space enumerate, read, modify, and delete draft Timeline objects that belong to other users in that same space, because object ownership is enforced through a user-controlled key rather than through a proper ACL check. Only Timeline read privilege is needed to enumerate and disclose other users' drafts, while the Timeline write privilege is additionally required to alter or delete them; the issue is therefore meaningful only in multi-user, shared Kibana spaces where Timeline privileges are granted to more than one principal, and it is rated CVSS 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L), indicating moderate confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); the vendor advisory referenced for this CVE points to the Kibana 8.19.22 and 9.4.6 security update (ESA-2026-103).
RemediationAI
The primary fix is to upgrade to the vendor-released patched versions identified in the referenced advisory, Elastic Kibana 8.19.22 or 9.4.6 (ESA-2026-103, see https://discuss.elastic.co/t/kibana-8-19-22-9-4-6-security-update-esa-2026-103/390679), which the vendor published to address this CVE; if the deployment is on a different branch, confirm the corresponding fixed build in that advisory before assuming the issue is resolved, because the supplied CPE data is version-wildcarded and does not itself enumerate the affected range. Where an immediate upgrade is not possible, compensating controls should target the privilege that enables the bypass: remove or reduce the Kibana Timeline feature privilege (especially Timeline write/all access) for roles in spaces where multiple users collaborate, which removes the ability to modify or delete other users' drafts and narrows enumeration to only those principals retaining Timeline read access, with the trade-off that legitimate Timeline collaboration in that space stops working for the demoted roles. Additional containment options are to restrict the number of distinct principals granted Timeline privileges within a given space so that each space has effectively a single Timeline user, eliminating the cross-user condition the vulnerability requires, at the cost of losing shared Timeline workflows; or to avoid storing sensitive content in draft Timelines until the upgrade is applied, since read access is sufficient for enumeration and disclosure and the write privileges are only needed for the destructive actions. These are risk-reduction measures only and do not fix the underlying authorization bypass, so the version upgrade to 8.19.22 or 9.4.6 should be scheduled regardless; post-upgrade, review Timeline privilege assignments across spaces to confirm the least-privilege posture, and audit Timeline objects for unexpected modification or deletion that may indicate prior exploitation, even though no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-639, Authorization Bypass Through User-Controlled Key, a classic insecure direct object reference (IDOR) pattern in which an application uses a key supplied or influenced by the requester to look up a resource without verifying that the requester is authorized to access that specific object. In Kibana's case the affected resource type is the draft Timeline object, and the containing security boundary is the Kibana space plus the Timeline feature privilege. Kibana's spaces model segments saved objects, and the Timeline feature privileges (read and write/all) are expected to constrain which Timeline saved objects a principal can see and mutate; here that per-object ownership constraint (CAPEC-1, Accessing Functionality Not Properly Constrained by ACLs) was not correctly applied, so a principal with Timeline read access in a space can reach other users' draft Timelines, and a principal with Timeline write access can also modify or delete them. Note that the flaw is entirely dependent on the authorization layer rather than on a memory-safety or code-execution primitive: the CVSS vector AV:N/AC:L/PR:L/UI:N/S:U with low C/I/A reflects an authenticated, network-reachable, no-user-interaction data-integrity and confidentiality problem confined to the same space. The supplied CPE, cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*, identifies Elastic Kibana generally but is version-wildcarded, so the exact affected version range must be taken from the vendor advisory rather than from the CPE alone.
Know when Kibana gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Network-reachable, low-complexity, but requires an authenticated user with the granted Timeline privilege (PR:L); impact is bounded to same-space draft Timelines so C/I/A are each Low.
Primary rating from Vendor (elastic).
CVSS VectorVendor: elastic
DescriptionCVE.org
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized disclosure, modification, and deletion of data via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user granted the Timeline feature privilege in a Kibana space could enumerate, read, modify, and delete draft Timeline objects belonging to other users in the same space. Read access is sufficient for enumeration and disclosure; the Timeline write privilege is required for modification and deletion.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
Authorization bypass in Kibana's Fleet package installation process lets an authenticated user who holds delegated Fleet
Privilege escalation in Elastic Kibana's Agent Builder component (versions 9.4.0-9.4.3) allows authenticated low-privile
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
EUVD-2026-87793
GHSA-hgww-7pvf-x93v
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB