Kibana can lead to information disclosure · Insecure Direct Object Reference
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 3 Nov 2026, 19:46 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 4.3 |
|---|
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 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ElasticKibana | Affected
| Fixed in– |
AI-suggested
Since the vulnerability requires authenticated access, review and restrict user permissions to minimize exposure. Monitor vendor advisories for updates or patches addressing this issue.
Description
CVE-2026-115295 is an authorization bypass vulnerability in Kibana where an authenticated user with read access to connectors in one space can access connector execution logs from other unauthorized spaces. The exposed information includes connector names, identifiers, execution status, timestamps, error messages, and aggregated execution statistics. This vulnerability is due to improper access control enforcement (CWE-639).