VulnerabilityPublished 11 Mar 2026Updated 12 Mar 2026

CVE-2026-20162: Splunk Enterprise · Cross-site Scripting

Affects Splunk EnterpriseSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.3 Medium · fixed in 10.0.3 : update Splunk Enterprise when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.0.3, 9.4.9, 9.3.9 +4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade Splunk to 10.0.3, 9.4.9 or 9.3.9 (Enterprise); 10.2.2510.4, 10.1.2507.15, 10.0.2503.11 or 9.3.2411.123 (Cloud Platform).

Affected software

Product	Affected	Fixed in
SplunkSplunk Enterprise	Affected >=10.0 <10.0.3	Fixed in 10.0.3
SplunkSplunk Enterprise	Affected >=9.4 <9.4.9	Fixed in 9.4.9
SplunkSplunk Enterprise	Affected >=9.3 <9.3.9	Fixed in 9.3.9
SplunkSplunk Cloud Platform	Affected >=10.2.2510 <10.2.2510.4	Fixed in 10.2.2510.4
SplunkSplunk Cloud Platform	Affected >=10.1.2507 <10.1.2507.15	Fixed in 10.1.2507.15
SplunkSplunk Cloud Platform	Affected >=10.0.2503 <10.0.2503.11	Fixed in 10.0.2503.11

AI-suggested

Upgrade affected Splunk Enterprise and Cloud Platform instances to the latest patched versions (at or above 10.2.0, 10.0.3, 9.4.9, and 9.3.9 for Enterprise).
Restrict the ability to create or modify Views to trusted, higher-privileged roles only, minimizing exposure to low-privileged users.
Implement strict input validation and output encoding in custom Views or dashboards to prevent injection of malicious scripts.
Conduct regular audits of user roles and permissions to ensure least privilege principles are enforced.
Enhance phishing awareness training for users to reduce the likelihood of victims triggering malicious payloads.
Monitor Splunk logs for unusual activity related to Views creation or modification endpoints.
Employ Content Security Policy (CSP) headers to restrict execution of unauthorized scripts in browsers accessing Splunk interfaces.
Use multi-factor authentication (MFA) to reduce risk of account compromise if session tokens are exposed.
Isolate Splunk management interfaces from general user networks where feasible to limit exposure.
Stay informed of vendor advisories and apply security patches promptly.

Description

In Splunk Enterprise versions below 10.2.0, 10.0.3, 9.4.9, and 9.3.9, and Splunk Cloud Platform versions below 10.2.2510.4, 10.1.2507.15, 10.0.2503.11, and 9.3.2411.123, a low-privileged user who does not hold the "admin" or "power" Splunk roles could craft a malicious payload when creating a View (Settings - User Interface - Views) at the `/manager/launcher/data/ui/views/_new` endpoint leading to a Stored Cross-Site Scripting (XSS) through a path traversal vulnerability. This could result in execution of unauthorized JavaScript code in the browser of a user. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.

Impact

The primary impact of CVE-2026-20162 is on confidentiality, as successful exploitation allows execution of arbitrary JavaScript in the browsers of authenticated users, potentially exposing session tokens, credentials, or sensitive information accessible in the user's session. This can lead to account compromise or unauthorized actions performed with the victim's privileges. The integrity impact is limited since the vulnerability does not allow direct modification of backend data or system configurations. Availability is not affected. The requirement for user interaction (phishing) and low privileges needed to craft the payload lower the overall risk but do not eliminate it, especially in environments with many users and complex role assignments. Organizations relying on Splunk Enterprise for security monitoring and incident response may face increased risk of lateral movement or data leakage if attackers exploit this vulnerability. The persistence of stored XSS means multiple users can be affected until the vulnerability is patched. Given Splunk's widespread use in critical infrastructure, finance, healthcare, and government sectors, the potential impact spans multiple industries and geographies. Attackers could leverage this vulnerability as part of a broader attack chain to gain footholds or exfiltrate data.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product 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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

advisory.splunk.com/advisories/SVD-2026-0301 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Mar 2026, 19:09 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats