CVE-2025-20368VulnerabilityPublished 1 Oct 2025

CVE-2025-20368: 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 5.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.7Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% 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:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 1 Oct 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. Immediate patching: Upgrade Splunk Enterprise and Splunk Cloud Platform to versions 9.4.4, 9.3.6, 9.2.8 or later where the vulnerability is fixed. 2. Role-based access control review: Restrict the ability to create or modify saved searches and view job inspection details to trusted users only, minimizing the risk of malicious payload creation. 3. Input validation and output encoding: Implement additional web application firewall (WAF) rules to detect and block suspicious scripts or payloads in Splunk web traffic. 4. User awareness: Educate users to be cautious when accessing saved searches or error messages from untrusted sources. 5. Monitoring and logging: Enable detailed logging of saved search creation and modification activities to detect anomalous behavior. 6. Network segmentation: Limit access to Splunk web interfaces to trusted networks and VPN users to reduce exposure. 7. Incident response readiness: Prepare to investigate and respond to potential XSS exploitation attempts, including session hijacking or unauthorized access.

Description

In Splunk Enterprise versions below 9.4.4, 9.3.6, and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.108, 9.3.2408.118 and 9.2.2406.123, a low privileged user that does not hold the admin or power Splunk roles could craft a malicious payload through the error messages and job inspection details of a saved search. This could result in execution of unauthorized JavaScript code in the browser of a user.

Impact

For European organizations, this vulnerability poses a significant risk especially in sectors heavily reliant on Splunk for security monitoring, compliance, and operational analytics, such as finance, telecommunications, healthcare, and government. Successful exploitation could lead to unauthorized disclosure of sensitive information, including session cookies or tokens, enabling attackers to impersonate legitimate users or gain further access within the environment. This could undermine trust in security monitoring systems and potentially facilitate lateral movement or data exfiltration. Since Splunk dashboards and saved searches are often accessed by multiple users, the risk of cross-user impact is elevated. Additionally, regulatory frameworks such as GDPR impose strict requirements on protecting personal data, and exploitation leading to data leakage could result in legal and financial penalties. The medium severity score suggests moderate urgency, but organizations should prioritize patching due to the critical role of Splunk in security operations and the potential for chained attacks.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Oct 2025, 16:18 UTC

Technical details

References

Community reviews

Related threats