Authorization Bypass Through User-Controlled Key in Kibana Leading to Information Disclosure

published 2026-11-03 6 d ago modified 2026-11-03 5 d ago also EUVD-2026-116076

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits: 0; none known

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.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 6 d ago (2026-11-03)

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

Elastic Kibana

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

discuss.elastic.co /t/kibana-8-19-24-9-4-9-9-5-6-security-update-esa-2026-206/391360

Sources

CVE List CVE-2026-115295
NVD CVE-2026-115295

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary