Skip to main content
VulnerabilityPublished Updated

CVE-2025-25015: Elastic Kibana · Prototype Pollution

Affects Elastic KibanaSource CVE Database V5

0

Not known to be exploited · CVSS 9.9 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Elastic KibanaAffected
  • =8.15.0
  • =8.17.0
Fixed in–

AI-suggested

To mitigate CVE-2025-25015, organizations should immediately upgrade Kibana to versions later than 8.17.2 once patches are released, as these versions restrict exploitability and likely include fixes. Until patches are available, restrict access to Kibana interfaces, especially limiting roles with Viewer and elevated privileges such as fleet-all, integrations-all, and actions:execute-advanced-connectors. Implement strict role-based access controls (RBAC) and audit user permissions to ensure minimal privilege principles are enforced. Monitor Kibana logs and network traffic for unusual file uploads or HTTP requests that could indicate exploitation attempts. Employ web application firewalls (WAF) with custom rules to detect and block suspicious payloads targeting prototype pollution vectors. Additionally, isolate Kibana servers within secure network segments and use multi-factor authentication (MFA) to reduce the risk of compromised credentials. Regularly review and update security policies and incident response plans to prepare for potential exploitation scenarios. Finally, maintain up-to-date backups of Kibana configurations and data to enable recovery in case of compromise.

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

References

Community reviews

Loading reviews…