Skip to main content
VulnerabilityPublished Updated

CVE-2026-72643: Kibana Agent Builder Leading to Disclosure · Incorrect Authorization

Affects kibanaSource GCVE Database

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

Not known to be exploited · CVSS 7.1 High : upgrade to 9.5.1 or 9.4.5 soon.

Data as of 17 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 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.5.1, 9.4.5
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 17 Nov 2026.

What to do

Upgrade kibana to 9.5.1 or 9.4.5.

Affected software

ProductAffectedFixed in
Bitnamikibanapkg:bitnami/kibanaOther threatsAffected
  • >=9.4.0 <9.4.5
  • >=9.5.0 <9.5.1
Fixed in
  • 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 versions 9.4.5 or later and 9.5.1 or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-72643 is a high severity vulnerability in Kibana Agent Builder where incorrect authorization logic allows users to access and modify private agents they do not own. The flaw arises because ownership is determined by comparing a stable user identifier or, if absent, the username. Since usernames are not unique across Elasticsearch authentication realms, distinct users with the same username in different realms are treated as the same owner. This leads to unauthorized disclosure and tampering of private agent configurations and instructions.

References

Community reviews

Loading reviews…