LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0531 is a denial-of-service flaw in Kibana Fleet. A low-privileged user with viewer-like access to agent policies can send a crafted bulk retrieval request that makes Kibana consume memory until it crashes, making the service unavailable to users.

Executive priority

Treat as a service availability risk. Prioritize environments where Kibana supports security operations, observability, or endpoint management, especially if many users have Fleet viewer access. It is not currently sourced as actively exploited.

Technical view

The issue is CWE-770, allocation of resources without limits or throttling, in Kibana Fleet. The CVSS 3.1 score is 6.5: network exploitable, low complexity, privileges required, no user interaction, and high availability impact. Sources do not indicate confidentiality or integrity impact.

Likely exposure

Exposure is most relevant to organizations running affected Kibana Fleet versions with users or integrations holding viewer-equivalent access to agent policies. Publicly reachable Kibana increases business impact, but exploitation still requires authenticated low-level privileges.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not listed as KEV in the source bundle. The attack outcome is service unavailability through memory exhaustion, not data theft or code execution.

Researcher notes

Affected version information in the bundle is limited and should be reconciled with Elastic’s advisory. Validation should focus on version, Fleet usage, role exposure, and availability symptoms. Do not assume broader Elastic Stack impact beyond Kibana Fleet from these sources.

Mitigation direction

  • Review Elastic advisory ESA-2026-04 for fixed versions and upgrade guidance.
  • Prioritize updating Kibana deployments using Fleet and agent policies.
  • Restrict Kibana and Fleet access to trusted networks where feasible.
  • Review viewer-equivalent roles with agent policy read access.
  • Monitor Kibana memory usage and crash events until remediated.

Validation and detection

  • Inventory Kibana versions and identify Fleet-enabled deployments.
  • Confirm whether users have viewer-equivalent access to agent policies.
  • Check whether the deployment matches affected versions in the CVE record.
  • Review Kibana logs for unexplained memory exhaustion or crashes.
  • Verify remediation against Elastic’s published security update.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0531 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-0531Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ElasticKibana7.10.0, 8.0.0, 9.0.0, 9.2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.