Skip to content
Fencer Intel
medium 6.5

CVE-2026-33459 json

Uncontrolled Resource Consumption in Kibana Leading to Denial of Service

published 7mo ago modified 2mo ago also BIT-elk-2026-33459 , BIT-kibana-2026-33459 , EUVD-2026-20521

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
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 user with access to the automatic import feature can submit specially crafted requests with excessively large input values. When multiple such requests are sent concurrently, the backend services become unstable, resulting in service disruption and deployment unavailability for all users.

Patch / fix

  • bitnami elk 8.19.14, 9.2.8, 9.3.3
  • bitnami kibana 8.19.14, 9.2.8, 9.3.3
  • elastic kibana 8.19.14, 9.2.8, 9.3.3
  • elasticsearch kibana 8.19.14, 9.2.8, 9.3.3

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

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

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.14
>=9.0.0, <9.2.8
>=9.3.0, <9.3.3
8.19.14
9.2.8
9.3.3
bitnami kibana
>=8.0.0, <8.19.14
>=9.0.0, <9.2.8
>=9.3.0, <9.3.3
8.19.14
9.2.8
9.3.3

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.