Skip to content
Fencer Vulns
high 7.1

CVE-2026-72629 json

Authorization Bypass Through User-Controlled Key in Kibana Leading to Cross-Space Access to Machine Learning Trained Models

published 2026-08-13 2 mo ago modified 2026-09-08 2 mo ago also BIT-elk-2026-72629 , BIT-kibana-2026-72629 , EUVD-2026-58289

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized cross-space access via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). The result is disclosure of inference output from a trained model in a different space that the user is not authorized to list, read, or use, which exposes the behavior of a model. The same pattern also reached the deployment stop and deployment update operations, allowing an active trained model deployment in another space to be stopped or to have its allocated resources altered.

Patch / fix

  • bitnami elk 8.19.20, 9.4.5, 9.5.1
  • bitnami kibana 8.19.20, 9.4.5, 9.5.1
  • elastic kibana 8.19.20, 9.4.5, 9.5.1
  • elasticsearch kibana 8.19.20, 9.4.5, 9.5.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.19.0, <8.19.20
>=9.0.0, <9.4.5
>=9.5.0, <9.5.1
8.19.20
9.4.5
9.5.1
bitnami kibana
>=8.19.0, <8.19.20
>=9.0.0, <9.4.5
>=9.5.0, <9.5.1
8.19.20
9.4.5
9.5.1

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

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.