# CVE-2026-82299: Elastic Kibana authorization bypass leading to information disclosure

Source: https://junglewise.ai/threats/cve-2026-82299-elastic-kibana-authorization-bypass-leading-to-information  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-03. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-82299 · Severity: medium · CVSS 6.5 · Published 2026-09-03

Kibana, a data visualization and exploration platform used to analyze logs and metrics, contains an authorization flaw that allows authenticated users to access sensitive information they should not be able to see. The vulnerability requires Fleet debugging interfaces to be enabled and affects all Kibana 9.x versions up to 9.5.2. An attacker with valid credentials can exploit incorrectly configured access controls to view confidential data.

Technologies: [Elastic Kibana](https://junglewise.ai/threats/technologies/kibana). Vendors: [Elastic](https://junglewise.ai/threats/vendors/elastic).

## Quick answers

**Is CVE-2026-82299 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82299 being exploited in the wild.

**How severe is CVE-2026-82299?** Medium severity, with a CVSS score of 6.5, published 3 September 2026.

**Which products and versions are affected?** Elastic Kibana 9.0.0 to 9.4.5, 9.5.0 to 9.5.2.

**Is there a fix for CVE-2026-82299?** A patch was published on 2026-09-03: Fixed in Kibana 9.4.6 and 9.5.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-82299 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-82299?** Check whether you run Elastic Kibana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

This is an Incorrect Authorization (CWE-863) vulnerability in Kibana that allows authenticated users to bypass access control checks via exploitation of misconfigured security levels (CAPEC-180). The vulnerability was introduced in version 9.0.0 and only affects the 9.x release line; version 8.x is unaffected. Exploitation requires: (1) an authenticated user account, (2) network access to Kibana, and (3) Fleet debugging interfaces to be enabled in the configuration. An attacker can achieve information disclosure by accessing resources outside their intended permission scope. The issue is resolved in Kibana versions 9.4.6 and 9.5.3; no workarounds are available for unpatched systems.

## Affected products

- Elastic Kibana 9.0.0 to 9.4.5, 9.5.0 to 9.5.2

## Timeline

- 2026-09-03: disclosed
- 2026-09-03: patched: Fixed in Kibana 9.4.6 and 9.5.3

## References

- [https://discuss.elastic.co/t/kibana-9-4-6-9-5-3-security-update-esa-2026-175/390163](https://discuss.elastic.co/t/kibana-9-4-6-9-5-3-security-update-esa-2026-175/390163)

## Related threats

- [Elastic Kibana authorization bypass in connector logs](https://junglewise.ai/threats/cve-2026-115295-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana path traversal in Fleet feature](https://junglewise.ai/threats/cve-2026-115294-improper-limitation-of-a-pathname-to-a-restricted-directory-cwe)
- [Elastic Kibana credential disclosure in Observability onboarding](https://junglewise.ai/threats/cve-2026-115293-insertion-of-sensitive-information-into-sent-data-cwe-201-in)
- [Elastic Kibana authorization bypass in Machine Learning](https://junglewise.ai/threats/cve-2026-115292-authorization-bypass-through-user-controlled-key-cwe-639-in)
- [Elastic Kibana incorrect authorization in Fleet settings](https://junglewise.ai/threats/cve-2026-102412-incorrect-authorization-cwe-863-in-kibana-can-lead-to-sensitive)