Skip to content
Fencer Intel
high 7.1

CVE-2026-72643 json

Incorrect Authorization in Kibana Agent Builder Leading to Disclosure and Tampering of Private Agents

published 2mo ago modified 2mo ago also BIT-elk-2026-72643 , BIT-kibana-2026-72643 , EUVD-2026-58288

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 32%
public exploits
0
none known

Summary

Kibana Agent Builder determines whether a caller owns a private agent by comparing a stable user identifier when one is recorded, and falling back to a comparison of the username when it is not. A username is not unique across Elasticsearch authentication realms, so two distinct principals that share a username in different realms are treated as the same owner. This discloses the configuration and instructions of an agent the caller does not own, and allows that agent to be altered or removed.

Patch / fix

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

Is CVE-2026-72643 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.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).

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:L/A:N
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami elk
>=9.4.0, <9.4.5
>=9.5.0, <9.5.1
9.4.5
9.5.1
bitnami kibana
>=9.4.0, <9.4.5
>=9.5.0, <9.5.1
9.4.5
9.5.1

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.