# CVE-2026-49096: Uncaught Exception in Kibana Cases Leading to Denial of Service

> An authenticated user can cause a denial of service in Kibana Cases by storing malformed link syntax in a comment, preventing case access for all users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** BIT-elk-2026-49096, BIT-kibana-2026-49096, GHSA-448j-qxg7-vqm3, MINI-4xfc-gwpg-7c3q, MINI-ffgw-58h5-fvj3, MINI-gc6q-9h5h-9w96, MINI-h2w3-x39m-qjjp, MINI-jjf9-4v7j-wr5j, MINI-mvfx-xv8v-47wq, MINI-ph2f-98p9-ffmx

## What is CVE-2026-49096?

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

### Official description

Uncaught Exception (CWE-248) in Kibana Cases can lead to denial of service via Input Data Manipulation (CAPEC-153). Malformed link syntax stored in a case comment was not rejected or sanitized when the comment was later formatted for display, and the resulting unhandled error prevented the affected case from being displayed. An authenticated user holding privileges to comment on a case could store such a comment, after which that case became inaccessible to every user who opened it until the stored comment was removed.

Weakness: CWE-248 (Uncaught Exception)

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

2 open source packages ship an affected version, including kibana and elk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kibana` | Bitnami | From 8.0.0 | 8.19.20, 9.3.5, 9.4.2 |
| `elk` | Bitnami | From 8.0.0 | 8.19.20, 9.3.5, 9.4.2 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.19.20, 9.3.5 or 9.4.2.

## Is CVE-2026-49096 being exploited?

There is no known exploitation of CVE-2026-49096 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-49096 and fix it if it is affected.

What it is: CVE-2026-49096 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 13 Aug 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-49096 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.0.0; fixed in 8.19.20, 9.3.5, 9.4.2
- elk (Bitnami): affected from 8.0.0; fixed in 8.19.20, 9.3.5, 9.4.2

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-49096/ (Markdown: https://insights.sbomify.com/CVE-2026-49096/index.md)
```

## Sources

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

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