# CVE-2025-25015: Kibana arbitrary code execution via prototype pollution

> Attackers can achieve arbitrary code execution in Kibana via prototype pollution triggered by crafted file uploads and HTTP requests.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 5 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** BIT-elk-2025-25015, BIT-kibana-2025-25015, GHSA-r96x-p6v3-j823

## What is CVE-2025-25015?

CVE-2025-25015 is a critical code injection vulnerability in Elastic Kibana, published on 5 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP requests.
In Kibana versions >= 8.15.0 and < 8.17.1, this is exploitable by users with the Viewer role. In Kibana versions 8.17.1 and 8.17.2 , this is only exploitable by users that have roles that contain all the following privileges: fleet-all, integrations-all, actions:execute-advanced-connectors

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-25015?

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.15.0 | 8.17.3 |
| `elk` | Bitnami | From 8.15.0 | 8.17.3 |

Products: Elastic Kibana.

## How do I fix CVE-2025-25015?

Upgrade kibana to 8.17.3 or later.

## Is CVE-2025-25015 being exploited?

There is no known exploitation of CVE-2025-25015 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-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)
- [CVE-2018-17246](https://insights.sbomify.com/CVE-2018-17246/): Code injection in Kibana (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25015 and fix it if it is affected.

What it is: CVE-2025-25015 is a critical code injection vulnerability in Elastic Kibana, published on 5 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25015 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.15.0; fixed in 8.17.3
- elk (Bitnami): affected from 8.15.0; fixed in 8.17.3

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

## Sources

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

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