Skip to main content
CVE-2026-72655VulnerabilityPublished Updated

Improperly Controlled Modification of Dynamically-Determined Object Attributes in Kibana Leading to Unauthorized Data

Affects kibanaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-72655· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 9.4.5 or 8.19.20 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.4.5, 8.19.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.4.5 or 8.19.20.

Affected software

ProductAffectedFixed in
Bitnamikibanapkg:bitnami/kibanaOther threatsAffected
  • >=8.0.0 <8.19.20
  • >=9.0.0 <9.4.5
Fixed in
  • 8.19.20
  • 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 Kibana to versions 8.19.20 or later, or 9.4.5 or later, where the authorization enforcement issue in the case management API has been fixed. No additional mitigation steps are indicated.

Description

A vulnerability in Kibana's Elastic Security case management allows authenticated users without case editing privileges to modify case data. This occurs because the case management API does not enforce the same authorization checks as the user interface, enabling low-privileged users to alter case records they should only view. The issue affects versions 8.0.0 up to but not including 8.19.20, and 9.0.0 up to but not including 9.4.5. A patch is available to address this improper authorization enforcement.

References

Community reviews

Loading reviews…