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

published 2026-07-21 3 mo ago modified 2026-10-24 15 d ago also BIT-elk-2026-63259 , BIT-kibana-2026-63259 , EUVD-2026-47585

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 21%
public exploits: 0; none known

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.

Patch / fix

fixed in 4

bitnami elk 9.4.4
bitnami kibana 9.4.4
elastic kibana 9.4.4
elasticsearch kibana 9.4.4

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 3 mo ago (2026-07-22)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% 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
OSV	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	elk	>=9.4.0, <9.4.4	9.4.4
bitnami	kibana	>=9.4.0, <9.4.4	9.4.4

Affected products

Elastic Kibana

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

discuss.elastic.co /t/kibana-9-4-4-security-update-esa-2026-70/388573
vendor-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2026-63259
web

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary