Skip to content
Fencer Intel
medium 6.5

CVE-2026-72659 json

Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service

published 2mo ago modified 2mo ago also BIT-elk-2026-72659 , BIT-kibana-2026-72659 , EUVD-2026-58270

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A specially crafted, malformed payload submitted to a Kibana visualization feature by an authenticated user holding only low-privileged access is not correctly validated before use. Processing the request causes unbounded memory growth in the Kibana process, which is terminated by the host once available memory is exhausted. Kibana then becomes unavailable to all users until the service is restarted.

Patch / fix

  • bitnami elk 8.19.20, 9.4.5
  • bitnami kibana 8.19.20, 9.4.5
  • elastic kibana 8.19.20, 9.4.5
  • elasticsearch kibana 8.19.20, 9.4.5

Is CVE-2026-72659 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.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elk
>=8.0.0, <8.19.20
>=9.0.0, <9.4.5
8.19.20
9.4.5
bitnami kibana
>=8.0.0, <8.19.20
>=9.0.0, <9.4.5
8.19.20
9.4.5

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

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.