Skip to main content
VulnerabilityPublished Updated

CVE-2026-72672: kibana · Incorrect Authorization

Affects kibanaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-72672· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.4.5 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (elastic)CVSS 3.16.5
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.4.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 17 Nov 2026.

What to do

Upgrade kibana to 9.4.5.

Affected software

ProductAffectedFixed in
Bitnamikibanapkg:bitnami/kibanaOther threatsAffected
  • >=9.1.0 <9.4.5
Fixed in
  • 9.4.5

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 affected Elastic Stack versions to 9.4.5 or later to remediate the issue. Since this is an authorization flaw, applying the official fix is the recommended mitigation.

Description

A vulnerability in Elastic Security's Kibana component allows authenticated users with Elastic Security feature privileges, but without read access to Elastic Defend event indices, to retrieve sensitive endpoint event data. This occurs because Kibana queries Elastic Defend event data using its internal Elasticsearch account rather than the requesting user's account, bypassing Elasticsearch index privilege checks. Sensitive information such as process command line arguments, which may include tokens, credentials, and connection strings, can be exposed. Versions 9.1.0 up to but not including 9.4.5 are affected. A patch is available to address this issue.

References

Community reviews

Loading reviews…