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

> Attackers can execute arbitrary code in Kibana by exploiting prototype pollution in machine learning and reporting endpoints via crafted HTTP requests.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** BIT-elk-2025-25014, BIT-kibana-2025-25014, GHSA-xpp5-m7fr-wp25

## What is CVE-2025-25014?

CVE-2025-25014 is a critical code injection vulnerability in Elastic Kibana, published on 6 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A Prototype pollution vulnerability in Kibana leads to arbitrary code execution via crafted HTTP requests to machine learning and reporting endpoints.

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

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

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.3.0 | 8.17.6, 8.17.10, 9.0.1 |
| `elk` | Bitnami | From 8.3.0 | 8.18.1, 9.0.1 |

Products: Elastic Kibana.

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

Upgrade kibana to a fixed version for your release line: 8.17.6, 8.17.10 or 9.0.1.

## Is CVE-2025-25014 being exploited?

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

Public exploit code:

- https://github.com/davidxbors/CVE-2025-25014 (github_poc): https://github.com/davidxbors/CVE-2025-25014

## 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-2025-25014 and fix it if it is affected.

What it is: CVE-2025-25014 is a critical code injection vulnerability in Elastic Kibana, published on 6 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25014 in the wild and no public exploit code.

Affected packages and fixed versions:
- kibana (Bitnami): affected from 8.3.0; fixed in 8.17.6, 8.17.10, 9.0.1
- elk (Bitnami): affected from 8.3.0; fixed in 8.18.1, 9.0.1

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

## Sources

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

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