Skip to main content
VulnerabilityPublished Updated

CVE-2026-72632: kibana · Observable Discrepancy

Affects kibanaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-72632· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in 9.5.1 : patch kibana soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.5.1, 9.4.5, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade kibana to 9.5.1, 9.4.5 or 8.19.20.

Affected software

ProductAffectedFixed in
Bitnamikibanapkg:bitnami/kibanaOther threatsAffected
  • >=8.19.0 <8.19.20
  • >=9.0.0 <9.4.5
  • >=9.5.0 <9.5.1
Fixed in
  • 8.19.20
  • 9.4.5
  • 9.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Users should upgrade Kibana to a fixed version to eliminate this side-channel information disclosure. The affected versions are >=8.19.0 <8.19.20, >=9.0.0 <9.4.5, and >=9.5.0 <9.5.1. No additional mitigations are indicated beyond applying the official fix.

Description

A vulnerability in Kibana Fleet allows an attacker to reconstruct Elasticsearch API keys of enrolled Elastic Agents via a side-channel attack. The flaw arises because Fleet removes API key values from agent listing responses but accepts caller-supplied filter expressions evaluated with elevated privileges. By observing the number of matching agents for crafted filters, an attacker can infer the API key characters one at a time.

References

Community reviews

Loading reviews…