Skip to content
Fencer Intel
high 7.1

CVE-2026-72632 json

Observable Discrepancy in Kibana Fleet Leading to Disclosure of Elastic Agent Elasticsearch API Keys

published 2mo ago modified 2mo ago also BIT-elk-2026-72632 , BIT-kibana-2026-72632 , EUVD-2026-58221

cvss
7.1
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 28%
public exploits
0
none known

Summary

Observable Discrepancy (CWE-203) in Kibana Fleet can lead to information disclosure via Excavation (CAPEC-116). Fleet removes the Elasticsearch API key value of an enrolled Elastic Agent from the responses of its agent listing capability, but that capability accepted caller-supplied filter expressions over the stored field that holds the value, and evaluated them with Kibana's own internal Elasticsearch privileges rather than the caller's. Because the number of matching agents is reported back to the caller, the difference between a matching and a non-matching filter formed a side channel from which the full API key value could be reconstructed one character at a time with a short sequence of requests.

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

Is CVE-2026-72632 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.35% chance of exploitation in the next 30 days, higher than 28% 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
>=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

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.