Skip to content
Fencer Intel
high 7.6

CVE-2026-72669 json

Missing Authorization in Kibana Leading to Cross-User Information Disclosure and Data Tampering

published 2mo ago modified 2mo ago also BIT-elk-2026-72669 , BIT-kibana-2026-72669 , EUVD-2026-58256

cvss
7.6
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 26%
public exploits
0
none known

Summary

The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flow, and the routes that read and update that state do not verify ownership. An authenticated user who holds only generic read access to the space can therefore discover the onboarding flows of other users, read their onboarding state, and write arbitrary progress data into them. A tampered flow can also cause the owner's onboarding view to fail with a server error.

Patch / fix

  • bitnami elk 8.19.19, 9.4.5
  • bitnami kibana 8.19.19, 9.4.5
  • elastic kibana 8.19.19, 9.4.5
  • elasticsearch kibana 8.19.19, 9.4.5

Is CVE-2026-72669 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.9.0, <8.19.19
>=9.0.0, <9.4.5
8.19.19
9.4.5
bitnami kibana
>=8.9.0, <8.19.19
>=9.0.0, <9.4.5
8.19.19
9.4.5

Affected products

  • Elastic Kibana

Classification

Weakness

References

Sources

Fencer Intel 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.