Skip to main content
CVE-2025-25018VulnerabilityPublished Updated

CVE-2025-25018: Elastic Kibana · XSS or 'Cross-site Scripting'

Affects Elastic KibanaSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Elastic KibanaAffected
  • =7.0.0
  • =8.0.0
  • =8.19.0
  • =9.0.0
  • =9.1.0
Fixed in–

AI-suggested

Organizations should immediately prepare to apply official patches from Elastic once they become available, as patching is the most effective mitigation. Until patches are released, administrators should restrict access to Kibana interfaces to trusted networks and users only, employing strong authentication and multi-factor authentication (MFA) to reduce the risk of unauthorized access. Implement strict input validation and output encoding on any custom plugins or integrations that interact with Kibana to minimize injection risks. Deploy Content Security Policies (CSP) to restrict the execution of untrusted scripts within Kibana’s web interface. Regularly audit Kibana user roles and permissions to enforce the principle of least privilege, limiting the number of users who can input or modify content that might be rendered in the UI. Monitor logs and network traffic for unusual activity indicative of attempted exploitation. Consider isolating Kibana instances from direct internet exposure using VPNs or reverse proxies with additional security controls. Finally, educate users about the risks of interacting with untrusted content within Kibana dashboards or visualizations.

Description

Improper Neutralization of Input During Web Page Generation in Kibana can lead to stored Cross-Site Scripting (XSS)

References

Community reviews

Loading reviews…