VulnerabilityPublished 13 Jan 2026

CVE-2026-0530: Elastic Kibana · Unthrottled Resource Allocation

Affects Elastic KibanaSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ElasticKibana	Affected >=7.10.0 <=7.17.29 >=8.0.0 <=8.19.9 >=9.0.0 <=9.1.9 >=9.2.0 <=9.2.3	Fixed in–

AI-suggested

Monitor Kibana Fleet request patterns for unusual or repetitive requests that could indicate exploitation attempts.
Implement rate limiting and resource throttling at the application or network level to prevent excessive resource consumption from individual clients.
Restrict access to Kibana Fleet interfaces to trusted users and networks, enforcing least privilege principles to reduce the risk from low-privilege accounts.
Deploy infrastructure-level resource controls such as container resource limits or cgroups to contain potential resource exhaustion.
Maintain up-to-date backups and incident response plans to quickly recover from potential service disruptions.
Stay informed on Elastic's official advisories and apply patches promptly once they become available.
Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with custom rules to detect and block malformed requests targeting this vulnerability.
Conduct regular security assessments and penetration tests focusing on resource exhaustion and denial of service vectors in Kibana deployments. These steps go beyond generic advice by emphasizing proactive monitoring, access control, and infrastructure-level resource management tailored to this specific vulnerability.

Description

CVE-2026-0530 is a medium severity vulnerability in Elastic Kibana Fleet affecting versions 7.10.0, 8.0.0, 9.0.0, and 9.2.0. It involves allocation of resources without limits or throttling (CWE-770), allowing an attacker with low privileges to send specially crafted requests that cause redundant processing and excessive resource consumption.

Impact

For European organizations, the primary impact of CVE-2026-0530 is on the availability of Kibana services, which are widely used for log analysis, monitoring, and operational intelligence. Service degradation or outages could impair incident response, security monitoring, and business analytics, leading to delayed detection of other threats or operational issues. Organizations in sectors such as finance, telecommunications, energy, and government that rely heavily on Elastic Stack for real-time data visualization and alerting may experience significant operational disruption. The vulnerability does not affect confidentiality or integrity, so data breaches or manipulation are not direct concerns. However, denial of service conditions could indirectly increase risk exposure by reducing visibility into system health and security events. The requirement for low privileges to exploit means insider threats or compromised accounts could leverage this vulnerability to cause disruption. The absence of known exploits currently limits immediate risk but also means organizations should proactively prepare. The impact is heightened in environments with high Kibana usage and limited resource isolation or monitoring.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

discuss.elastic.co/t/kibana-8-19-10-9-1-10-9-2-4-security-update-esa-2026-03/384521 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 02:54 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats