CVE-2026-72667: CWE-770 Allocation of Resources Without Limits or Throttling in Elastic Kibana
Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). A specially crafted request submitted by an authenticated user with minimal privileges to a validation capability of the Observability log analysis feature causes Kibana to perform an unbounded amount of concurrent work. This can exhaust the memory available to the Kibana process and make Kibana unavailable to all users until it is restarted. The severity of the outcome depends on the resources allocated to the deployment; on well-provisioned deployments a single request may cause degraded performance and elevated memory pressure rather than a full outage, but the request is inexpensive to repeat.
AI Analysis
Technical Summary
This vulnerability (CWE-770) in Elastic Kibana allows an authenticated user with minimal privileges to submit a specially crafted request to the validation capability of the Observability log analysis feature. The request triggers unbounded concurrent processing, exhausting memory resources of the Kibana process. This results in denial of service by making Kibana unavailable until restarted. The severity depends on deployment resource allocation; well-provisioned deployments may experience degraded performance and elevated memory pressure rather than complete outage. The vulnerability affects Kibana versions 8.0.0 and 9.0.0. No known exploits are reported in the wild, and no official remediation or patch is currently documented.
Potential Impact
The vulnerability can cause denial of service by exhausting memory resources of the Kibana process, making the service unavailable until it is restarted. On deployments with ample resources, the impact may be limited to degraded performance and increased memory pressure. The attack requires authenticated access with minimal privileges and does not affect confidentiality or integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider restricting access to the Observability log analysis feature to trusted users and monitor resource usage to detect potential abuse. Restarting Kibana can restore service availability after an attack.
CVE-2026-72667: CWE-770 Allocation of Resources Without Limits or Throttling in Elastic Kibana
Description
Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). A specially crafted request submitted by an authenticated user with minimal privileges to a validation capability of the Observability log analysis feature causes Kibana to perform an unbounded amount of concurrent work. This can exhaust the memory available to the Kibana process and make Kibana unavailable to all users until it is restarted. The severity of the outcome depends on the resources allocated to the deployment; on well-provisioned deployments a single request may cause degraded performance and elevated memory pressure rather than a full outage, but the request is inexpensive to repeat.
CVSS v3.1
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-770) in Elastic Kibana allows an authenticated user with minimal privileges to submit a specially crafted request to the validation capability of the Observability log analysis feature. The request triggers unbounded concurrent processing, exhausting memory resources of the Kibana process. This results in denial of service by making Kibana unavailable until restarted. The severity depends on deployment resource allocation; well-provisioned deployments may experience degraded performance and elevated memory pressure rather than complete outage. The vulnerability affects Kibana versions 8.0.0 and 9.0.0. No known exploits are reported in the wild, and no official remediation or patch is currently documented.
Potential Impact
The vulnerability can cause denial of service by exhausting memory resources of the Kibana process, making the service unavailable until it is restarted. On deployments with ample resources, the impact may be limited to degraded performance and increased memory pressure. The attack requires authenticated access with minimal privileges and does not affect confidentiality or integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider restricting access to the Observability log analysis feature to trusted users and monitor resource usage to detect potential abuse. Restarting Kibana can restore service availability after an attack.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:45.103Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a84bf8831d539b1836d
Added to database: 08/13/2026, 19:27:00 UTC
Last enriched: 08/13/2026, 19:44:21 UTC
Last updated: 08/13/2026, 21:47:26 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.