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