Assessment
Why it matters
EPSS is 0.3%; technical severity is CVSS 6.5.
Incorrect Authorization (CWE-863) in Kibana can lead to information disclosure via Privilege Abuse (CAPEC-122). A user with limited Fleet privileges can exploit an internal API endpoint to retrieve sensitive configuration data, including private keys and authentication tokens, that should only be accessible to users with higher-level settings privileges. The endpoint composes its response by fetching full configuration objects and returning them directly, bypassing the authorization checks enforced by the dedicated settings APIs.
Who should care
- Teams operating Kibana
- Vulnerability and exposure management teams
- Security operations teams monitoring exploitation activity
Response plan
What I would do
- Confirm whether Kibana is present in the environment.
- Identify affected versions and establish whether vulnerable services are exposed or reachable.
- Vendor advisory from discuss.elastic.co
- Review relevant security telemetry for evidence of attempted or successful exploitation.
- Document the remediation decision and track it to verified completion.
Treatment intelligence
Remediation intelligence
Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.
Technical details
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CWE
- CWE-863
- Affected versions
- Elastic Kibana (Start Including 8.0.0, End Excluding 8.19.14 | Start Including 9.0.0, End Excluding 9.2.8 | Start Including 9.3.0, End Excluding 9.3.3)
- Fixed versions
- Elastic Kibana (Fixed from 8.19.14, 9.2.8, 9.3.3)
- Published
- 8 April 2026
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
Signal timeline
- CVE published
- Latest EPSS score: 0.3%
- Signal calculated at 11