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.
Published: 2026-08-13
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A request handling flaw in Kibana lets an authenticated user with minimal privileges send a specially crafted payload to the Observability log analysis validation endpoint, causing the service to spawn an unbounded amount of concurrent work. The resulting memory exhaustion can bring the Kibana process to a halt or degrade performance, impacting all users until the service is restarted. The weakness matches CWE‑770, which describes allocations made without bounds or throttling.

Affected Systems

The vulnerability affects Elastic’s Kibana product. No specific release versions are disclosed in the CVE data.

Risk and Exploitability

The CVSS score is 6.5, indicating a medium severity. No EPSS value is published, so the exploitation likelihood is unknown from the data; the issue is not listed in the CISA KEV catalog. Attack requires a valid user account with access to the Observability feature, which is usually granted to any authenticated user, making the attack vector relatively low‑barrier. An attacker could repeat the request to exacerbate the impact, potentially leading to a full service outage if the deployment lacks sufficient resources.

Generated by OpenCVE AI on August 13, 2026 at 21:58 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Kibana to a version that includes the vendor‑provided fix for the resource‑exhaustion flaw.
  • If an immediate upgrade is not feasible, disable or restrict the Observability log analysis feature for users with minimal privileges, limiting their ability to trigger the vulnerable endpoint.
  • Configure operating‑system or container resource limits to cap the memory usage of the Kibana process, ensuring that a single process cannot consume all available RAM.
  • Set up monitoring and alerting for high memory consumption or unresponsive Kibana instances so that rapid action can be taken before an outage occurs.

Generated by OpenCVE AI on August 13, 2026 at 21:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Elastic
Elastic kibana
Vendors & Products Elastic
Elastic kibana
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 13 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
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.
Title Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service
Weaknesses CWE-770
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: elastic

Published:

Updated: 2026-08-13T20:31:37.225Z

Reserved: 2026-08-10T11:17:45.103Z

Link: CVE-2026-72667

cve-icon Vulnrichment

Updated: 2026-08-13T20:31:33.663Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-13T20:17:27.283

Modified: 2026-08-28T15:32:26.217

Link: CVE-2026-72667

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T22:00:05Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling