CVE-2025-20385VulnerabilityPublished 3 Dec 2025

CVE-2025-20385: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Splunk Splunk Enterprise	Affected =10.0 =9.4 =9.3 =9.2	Fixed in–

AI-suggested

1. Apply the vendor-provided patches by upgrading Splunk Enterprise to version 10.0.2 or later, 9.4.6 or later, 9.3.8 or later, and 9.2.10 or later, or the corresponding patched versions of Splunk Cloud Platform. 2. Restrict the assignment of the 'admin_all_objects' capability strictly to trusted and necessary personnel to reduce the attack surface. 3. Implement Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers accessing Splunk web interfaces. 4. Regularly audit Splunk navigation bar collections and other user-controllable inputs for suspicious or unauthorized modifications. 5. Educate users with high privileges about phishing and social engineering risks to prevent attackers from gaining initial access. 6. Monitor Splunk logs for unusual activity related to navigation bar modifications or administrative actions. 7. Consider deploying web application firewalls (WAFs) with rules to detect and block XSS payloads targeting Splunk interfaces. These steps go beyond generic advice by focusing on privilege management, input auditing, and layered defenses specific to the Splunk environment.

Description

In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and Splunk Cloud Platform versions below 10.1.2507.6, 10.0.2503.7, and 9.3.2411.117, a user who holds a role with a high privilege capability `admin_all_objects` could craft a malicious payload through the href attribute of an anchor tag within a collection in the navigation bar, which could result in execution of unauthorized JavaScript code in the browser of a user.

Impact

For European organizations, the primary impact is the potential for unauthorized JavaScript execution in the browsers of users who access the compromised navigation bar collections. This could lead to limited confidentiality breaches such as session token theft or unauthorized actions performed in the context of the victim user. However, since exploitation requires an attacker to already have high-level administrative privileges and user interaction, the risk of widespread compromise is low. Organizations relying on Splunk for security monitoring and operational intelligence could face targeted attacks aimed at elevating privileges or stealing sensitive monitoring data if the vulnerability is exploited. The impact on integrity and availability is negligible. Nonetheless, in environments with strict compliance requirements (e.g., GDPR), even low-severity vulnerabilities that could lead to data leakage must be addressed promptly. The absence of known exploits in the wild reduces immediate risk but does not eliminate the need for remediation.

References

advisory.splunk.com/advisories/SVD-2025-1204 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Dec 2025, 18:34 UTC

Technical details

References

Community reviews

Related threats