# CVE-2026-49087: Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of Service

> An authenticated user can cause a denial of service in Kibana by submitting a crafted bulk deletion request that exhausts resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-fv98-p2r6-2cjr, MINI-2q3h-2r9q-gjcg, MINI-8pm4-3m87-96f7, MINI-9wp5-936q-9jmm, MINI-q4wx-vrrm-vgr2, MINI-wf3m-8x67-3pjc, MINI-xpcr-jr9g-9x2g

## What is CVE-2026-49087?

CVE-2026-49087 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user can submit a specially crafted bulk deletion request that causes excessive resource consumption, which may render Kibana unavailable.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-49087?

It affects 1 product.


Products: Elastic Kibana.

## How do I fix CVE-2026-49087?

Upgrade to a fixed version.

## Is CVE-2026-49087 being exploited?

There is no known exploitation of CVE-2026-49087 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Kibana

- [CVE-2019-7609](https://insights.sbomify.com/CVE-2019-7609/): Kibana Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-25015](https://insights.sbomify.com/CVE-2025-25015/): Kibana arbitrary code execution via prototype pollution (critical 9.9)
- [CVE-2024-37288](https://insights.sbomify.com/CVE-2024-37288/): Deserialization in Kibana (critical 9.9)
- [CVE-2023-31415](https://insights.sbomify.com/CVE-2023-31415/): Code injection in Kibana (critical 9.9)
- [CVE-2018-17245](https://insights.sbomify.com/CVE-2018-17245/): Information disclosure in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49087 and fix it if it is affected.

What it is: CVE-2026-49087 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49087 in the wild and no public exploit code.

Affected product: Elastic Kibana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49087/ (Markdown: https://insights.sbomify.com/CVE-2026-49087/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49087
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49087
- OSV: https://osv.dev/vulnerability/CVE-2026-49087

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49087/
Summaries are generated and may contain mistakes; the official description above is the record.