# CVE-2026-115295: Elastic Kibana authorization bypass in connector logs

Source: https://junglewise.ai/threats/cve-2026-115295-authorization-bypass-through-user-controlled-key-cwe-639-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-115295 · Severity: medium · CVSS 4.3 · Published 2026-11-03

Kibana, an analytics and visualization platform used to explore and manage data, contains an authorization flaw that allows authenticated users to view connector execution logs from spaces they should not have access to. An attacker with legitimate read access to connectors in one workspace can discover connector names, identifiers, error messages, and execution details from other restricted workspaces, potentially exposing sensitive operational information.

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

## Quick answers

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

**How severe is CVE-2026-115295?** Medium severity, with a CVSS score of 4.3, published 3 November 2026.

**Which products and versions are affected?** Elastic Kibana 8.7.0 to 8.19.23; 9.0.0 to 9.4.8; 9.5.0 to 9.5.5.

**Is there a fix for CVE-2026-115295?** Yes: fixed in Kibana 8.19.24, 9.4.9, 9.5.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115295 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-115295?** 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.

## How to fix

- Fixed in Kibana 8.19.24, 9.4.9, 9.5.6

## Technical details

An authorization bypass vulnerability (CWE-639) in Kibana's connector execution log retrieval allows an authenticated user with read-only connector access in one space to access logs from other spaces via user-controlled key manipulation. The vulnerability affects multi-space deployments and requires authentication and pre-existing connector access. No privilege escalation or data modification is possible; the impact is limited to information disclosure of connector metadata and execution details.

## Affected products

- Elastic Kibana 8.7.0 to 8.19.23; 9.0.0 to 9.4.8; 9.5.0 to 9.5.5

## Timeline

- 2026-11-03: disclosed

## References

- [https://discuss.elastic.co/t/kibana-8-19-24-9-4-9-9-5-6-security-update-esa-2026-206/391360](https://discuss.elastic.co/t/kibana-8-19-24-9-4-9-9-5-6-security-update-esa-2026-206/391360)

## Related threats

- [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)
- [Elastic Kibana missing authorization in Metrics Experience](https://junglewise.ai/threats/cve-2026-102410-missing-authorization-cwe-862-in-kibana-can-lead-to-information)
