Skip to content
Fencer Intel
medium 6.5

CVE-2026-63260 json

Uncontrolled Resource Consumption in Kibana Leading to Denial of Service

published 3mo ago modified 18d ago also BIT-elk-2026-63260 , BIT-kibana-2026-63260 , EUVD-2026-47588

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

Summary

Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.

Patch / fix

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

Is CVE-2026-63260 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
3mo ago

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 41% 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.19
>=9.0.0, <9.3.8
>=9.4.0, <9.4.4
8.19.19
9.3.8
9.4.4
bitnami kibana
>=8.0.0, <8.19.19
>=9.0.0, <9.3.8
>=9.4.0, <9.4.4
8.19.19
9.3.8
9.4.4

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.