Cyber Resilience

CVE-2025-25014

Elastic Kibana 8.3.0 – 8.17.6

Published
06 May 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.21 97th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2025-25014 is a critical-severity Prototype Pollution (CWE-1321) vulnerability in Elastic Kibana. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

This vulnerability is AI-related — categorised as Other Platforms; in the Other ATLAS/OWASP Terms risk domain.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A Prototype pollution vulnerability tracked as CVE-2025-25014 affects Kibana and permits arbitrary code execution when an attacker sends crafted HTTP requests to the machine learning and reporting endpoints. The flaw is classified under CWE-1321 and carries a CVSS 3.1 score of 9.1, reflecting network attack vector, low attack complexity, high privileges required, and changed scope with full impact on confidentiality, integrity, and availability.

An authenticated attacker with administrative access can exploit the issue over the network to execute arbitrary code on the Kibana host, potentially compromising the entire Elastic Stack deployment and any data it processes.

Elastic's security advisory directs users to upgrade Kibana to versions 8.17.6, 8.18.1, or 9.0.1 to remediate the vulnerability.

The associated EPSS score remains flat at 0.0254 with no observed increase after disclosure.

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-1321

AI Security AnalysisAI

AI Category
Other Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: machine learning

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-25015Same product: Elastic Kibana
CVE-2024-12556Same product: Elastic Kibana
CVE-2024-37287Same product: Elastic Kibana
CVE-2026-49091Same product: Elastic Kibana
CVE-2026-26936Same product: Elastic Kibana
CVE-2024-37285Same product: Elastic Kibana
CVE-2024-37288Same product: Elastic Kibana
CVE-2026-33463Same product: Elastic Kibana
CVE-2024-11390Same product: Elastic Kibana
CVE-2026-49095Same product: Elastic Kibana

Affected Assets

elastic
kibana
8.18.0, 9.0.0 · 8.3.0 — 8.17.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References