Skip to content
Fencer Intel
medium 6.5

CVE-2026-72631 json

Improper Privilege Management in Kibana Fleet Leading to Over-Scoped Elastic Agent API Keys

published 2mo ago modified 2mo ago also BIT-elk-2026-72631 , BIT-kibana-2026-72631 , EUVD-2026-58220

cvss
6.5
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

Improper Privilege Management (CWE-269) in Kibana Fleet can lead to privilege escalation via Privilege Escalation (CAPEC-233). An integration policy may optionally declare extra data streams that the integration writes to, which Fleet adds to the Elasticsearch API key issued to Elastic Agents enrolled in the corresponding agent policy. The resulting key allows new documents to be inserted and index mappings to be extended for specific indices. The key does not allow reading, updating, or deleting existing documents

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

Affected packages

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

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-269 Improper Privilege Management

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.