Skip to content
Fencer Intel
medium 6.5

CVE-2026-72674 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-72674 , BIT-kibana-2026-72674 , EUVD-2026-58261

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 a denial of service via Excessive Allocation (CAPEC-130). A user-supplied list of document fields accepted by the Kibana Playground for RAG feature was neither bounded in length nor de-duplicated before it was used to assemble the response for each matching document. A single crafted request could therefore make Kibana build a response far larger than the data it was derived from, and the resulting processing and memory pressure exhausts the resources of the Kibana instance.

Patch / fix

  • bitnami elk 9.3.8, 9.4.4
  • bitnami kibana 9.3.8, 9.4.4
  • elastic kibana 9.3.8, 9.4.4
  • elasticsearch kibana 9.3.8, 9.4.4

Is CVE-2026-72674 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
>=9.3.0, <9.3.8
>=9.4.0, <9.4.4
9.3.8
9.4.4
bitnami kibana
>=9.3.0, <9.3.8
>=9.4.0, <9.4.4
9.3.8
9.4.4

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.