Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS score of 4.3 (Low severity) reflects the limited immediate impact: the attack requires prior authentication with Fleet management permissions (PR:L), operates over the network without user interaction (AV:N, AC:L, UI:N), and results only in confidentiality loss (C:L) with no integrity or availability impact (I:N, A:N). However, real-world risk is elevated by several factors: the vulnerability enables privilege escalation within a multi-tenant environment where users may be intentionally restricted to specific spaces for data governance or compliance reasons, the disclosed information (policy details, infrastructure links) can enable lateral movement or reconnaissance for targeted attacks, and the presence of a simple enrollment endpoint suggests likely ease of exploitation. The EPSS score is not provided, but exploitation probability is moderate given the straightforward nature of bypassing authorization checks via an existing endpoint. This is not a critical vulnerability by CVSS standards, but organizations with strict multi-space segregation policies should prioritize remediation due to the breach of intended access boundaries. |
| Exploit ScenarioDerived | An authenticated Kibana user with Fleet agent management privileges in Space A logs in and crafts a request to the internal enrollment endpoint, specifying a policy identifier from Space B (obtained through reconnaissance or directory enumeration). The endpoint, lacking space validation, returns the full policy details without verifying the user's authorization to Space B, exposing infrastructure configuration and policy names. The attacker uses this information to understand the target environment's Fleet deployment and identify potential vulnerabilities or misconfigurations across spaces they should not access. No public proof-of-concept has been identified at time of analysis, but the straightforward nature of the authorization bypass (missing validation check on a standard endpoint) suggests exploitation is straightforward for threat actors with valid Kibana credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 08, 2026
Kibana's Fleet agent management endpoint fails to enforce space-scoped access controls, allowing authenticated users with Fleet privileges in one space to retrieve sensitive Fleet Server policy details from unauthorized spaces including policy names, operational identifiers, and infrastructure linkage information. The vulnerability affects Kibana across multiple versions and requires valid user authentication with Fleet agent management permissions, resulting in cross-space information disclosure without the ability to modify data.
RemediationAI
Update Kibana to the patched version specified in Elastic Security Update ESA-2026-25 (https://discuss.elastic.co/t/kibana-8-19-14-9-2-8-9-3-3-security-update-esa-2026-25/385813), which includes fixed versions 8.19.14, 9.2.8, and 9.3.3 or later depending on your deployment track. The primary fix enforces space-scoped authorization checks on the internal enrollment endpoint to prevent unauthenticated cross-space policy retrieval. If immediate patching is not possible, restrict network access to the Kibana Fleet enrollment endpoint to trusted Fleet servers only, and audit Kibana logs for suspicious policy retrieval requests from users accessing spaces outside their authorized scope.
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
Kibana's multi-tenancy architecture uses spaces to segregate user access and data visibility. The vulnerability exists in an internal enrollment endpoint used by Fleet agents to retrieve policy configurations. The endpoint uses an unscoped internal client (likely instantiated without space context) rather than enforcing space-scoped access controls through Kibana's authorization framework. This allows the endpoint to bypass the authorization checks that normally restrict users to their assigned space. CWE-863 (Incorrect Authorization) identifies the root cause: the system fails to verify that the authenticated user has permission to access resources in the requested space before returning sensitive Fleet Server configuration details.
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:N/A:N
Primary rating from Vendor (elastic) · only source for this CVE.
CVSS VectorVendor: elastic
DescriptionCVE.org
Incorrect Authorization (CWE-863) in Kibana can lead to cross-space information disclosure via Privilege Abuse (CAPEC-122). A user with Fleet agent management privileges in one Kibana space can retrieve Fleet Server policy details from other spaces through an internal enrollment endpoint. The endpoint bypasses space-scoped access controls by using an unscoped internal client, returning operational identifiers, policy names, management state, and infrastructure linkage details from spaces the user is not authorized to access.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-20523
GHSA-998c-7hf5-g249
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB