CVE-2026-0531 | Allocation of Resources Without Limits or Throttling in Kibana Fleet

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.

Published: 2026-01-13 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-0531 is rated Low Risk (37.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.42%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-0531

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.42% +0.36%
2 2026-02-14 0.04% 0.05% +0.01%
3 2026-01-14 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-0531

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2026-0531

OS Trackers for CVE-2026-0531

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2026-0531

Affected software / configurations for CVE-2026-0531

Vendor Product Version Raw CPE
elastic kibana >= 7.10.0, < 7.17.29 cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*
elastic kibana >= 8.0.0, < 8.19.10 cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*
elastic kibana >= 9.0.0, < 9.1.10 cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*
elastic kibana >= 9.2.0, < 9.2.4 cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*

References for CVE-2026-0531

cvelogic Threat Intelligence