Skip to main content
VulnerabilityPublished

CVE-2026-115295: Elastic Kibana · Insecure Direct Object Reference

Affects Elastic KibanaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 3 Nov 2026, 17:58 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (elastic)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
ElasticKibanaAffected
  • >=8.7.0 <=8.19.23
  • >=9.0.0 <=9.4.8
  • >=9.5.0 <=9.5.5
Fixed in–

AI-suggested

Until a fix is available, restrict read access to connectors to trusted users only and monitor for updates from Elastic regarding patches.

Description

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user with read access to connectors in one Kibana space can retrieve connector execution log information from other spaces that they are not authorized to access. The disclosed information includes connector names and identifiers, execution status, timestamps, error messages, and aggregated execution statistics.

References

Community reviews

Loading reviews…