LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0530: Allocation of Resources Without Limits or Throttling in Kibana Leading to Excessive Allocation

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted request. This causes the application to perform redundant processing operations that continuously consume system resources until service degradation or complete unavailability occurs.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0530 is a Kibana Fleet denial-of-service issue. An authenticated attacker with low privileges can send a crafted request that makes Kibana waste resources until performance degrades or the service becomes unavailable. The business impact is operational disruption, not data theft or tampering based on the CVSS vector.

Executive priority

Treat as a near-term availability risk for Kibana Fleet environments. Prioritize remediation where Kibana supports security operations, endpoint management, or other critical workflows. The issue is moderate overall, but downtime could have high operational impact.

Technical view

The CVE describes CWE-770 resource allocation without limits or throttling in Kibana Fleet. The reported impact is excessive allocation through redundant processing operations, causing high availability impact. CVSS 3.1 is 6.5: network-accessible, low attack complexity, low privileges required, no user interaction, no confidentiality or integrity impact.

Likely exposure

Exposure is most relevant where Kibana Fleet is enabled and reachable by authenticated users, especially internet-facing or broadly accessible Kibana deployments. The source lists Elastic Kibana versions 7.10.0, 8.0.0, 9.0.0, and 9.2.0 in the affected data, with default status otherwise unaffected.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires network access and low privileges. The described outcome is resource exhaustion leading to service degradation or complete unavailability, not code execution.

Researcher notes

Evidence is limited to the CVE record and Elastic advisory reference. The affected-version data in the provided bundle is terse, so validate exact fixed and affected versions directly with Elastic. Avoid assuming active exploitation because KEV is false and no cited source confirms exploitation.

Mitigation direction

  • Review Elastic’s linked security update for applicable fixed versions and upgrade guidance.
  • Prioritize externally reachable or shared Kibana Fleet deployments.
  • Restrict Kibana access to trusted users and networks where operationally possible.
  • Monitor Kibana resource use and availability for abnormal spikes.
  • If unable to update promptly, follow Elastic’s advisory for compensating controls.

Validation and detection

  • Inventory Kibana instances and identify those using Fleet.
  • Compare installed versions against the CVE record and Elastic advisory.
  • Confirm whether Kibana is reachable by low-privileged authenticated users.
  • Review logs and metrics for unexplained resource exhaustion or availability drops.
  • Document upgrade status and remaining exposed instances.
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
cve · low confidence lookup

CVE-2026-0530 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-0530Attack 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.