CVE-2026-115295: Kibana Leading to Information Disclosure · Insecure Direct Object Reference
Affects kibanaSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium · fixed in 9.5.6 : update kibana when convenient.
Data as of 17 Nov 2026, 16:49 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 9.5.6, 9.4.9, 8.19.24
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade kibana to 9.5.6, 9.4.9 or 8.19.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikibanapkg:bitnami/kibanaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and fixed versions include 8.19.24, 9.4.9, and 9.5.6. Users should upgrade to these versions or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
A vulnerability in Kibana allows an authenticated user with read access to connectors in one space to access connector execution log information from other spaces without proper authorization. This leads to information disclosure including connector names, identifiers, execution status, timestamps, error messages, and aggregated execution statistics. The issue is due to authorization bypass through a user-controlled key. Fixed versions are available.