Skip to content
Fencer Intel
medium 6.5

CVE-2026-0531 json

Allocation of Resources Without Limits or Throttling in Kibana Fleet

published 9mo ago modified 2mo ago also BIT-elk-2026-0531 , BIT-kibana-2026-0531 , EUVD-2026-2038

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 42%
public exploits
0
none known

Summary

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted bulk retrieval request. This requires an attacker to have low-level privileges equivalent to the viewer role, which grants read access to agent policies. The crafted request can cause the application to perform redundant database retrieval operations that immediately consume memory until the server crashes and becomes unavailable to all users.

Patch / fix

  • bitnami elk 8.19.10, 9.1.10, 9.2.4
  • bitnami kibana 8.19.10, 9.1.10, 9.2.4
  • elastic kibana 8.19.10, 9.1.10, 9.2.4
  • elasticsearch kibana 8.19.10, 9.1.10, 9.2.4

Is CVE-2026-0531 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-0531 updated cvss 6.5

kibana: allocation of resources without limits or throttling via specially crafted bulk retrieval request

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9mo ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% 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.19.10
>=9.0.0, <9.1.10
>=9.2.0, <9.2.4
8.19.10
9.1.10
9.2.4
bitnami kibana
<8.19.10
>=9.0.0, <9.1.10
>=9.2.0, <9.2.4
8.19.10
9.1.10
9.2.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.