dbcve.org
SplunkApplication

CVE-2026-20162

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 9.3.9 / 9.3.2411.123 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored cross-site scripting vulnerability exists in Splunk Enterprise and Cloud Platform where low-privileged users can inject malicious JavaScript payloads through path traversal when creating Views at the /manager/launcher/data/ui/views/_new endpoint. The crafted payload persists in the View configuration and executes when other users access the affected View, requiring phishing to trigger the malicious request.

MitigationUpgrade to Splunk Enterprise versions 10.2.0, 10.0.3, 9.4.9, 9.3.9 or later, or Splunk Cloud Platform versions 10.2.2510.4, 10.1.2507.15, 10.0.2503.11, 9.3.2411.123 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:>= 9.3.0, < 9.3.9>= 9.4.0, < 9.4.9>= 10.0.0, < 10.0.3
Splunk Cloud PlatformApplication
Affected:>= 9.3.2411, < 9.3.2411.123>= 10.0.2503, < 10.0.2503.11>= 10.1.2507, < 10.1.2507.15>= 10.2.2510, < 10.2.2510.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Splunk Enterprise version
    Run the command: splunk --version or access About > Version in the Splunk web interface. For Splunk Cloud, check the version in the Cloud Portal or via support.
    Affected if The version falls within >= 9.3.0 and < 9.3.9, or >= 9.4.0 and < 9.4.9, or >= 10.0.0 and < 10.0.3 for Enterprise; or the Cloud Platform versions match the affected ranges listed in the CVE.
  2. Identify accessible View configurations
    Navigate to Settings > Views or query the internal index for saved views: | rest /services/data/ui/views | fields title eai:acl.app eai:data
    Affected if Any View configuration contains HTML script tags, javascript:, or encoded XSS patterns in the view XML definition.
  3. Audit View creation via the views/_new endpoint
    Search Splunk audit logs for POST requests to /manager/launcher/data/ui/views/_new: index=_internal sourcetype=splunkd_access method=POST uri=*/manager/launcher/data/ui/views/_new | stats count by user src_ip uri
    Affected if Low-privileged users (non-admin) have created Views through this endpoint.
  4. Examine View XML for path traversal or script injection
    Review the eai:data field from the saved views: | rest /services/data/ui/views | fields title eai:data | search eai:data IN (*script*, *javascript*, *onerror*, *onload*)
    Affected if The View XML contains malicious JavaScript payloads, encoded scripts, or path traversal sequences used to inject XSS.

A user is affected if they are running a Splunk version within the affected ranges AND low-privileged users have access to create Views that contain injected JavaScript in the View configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3.9 / 9.3.2411.123 / 9.4.9 or later
Fixed in 9.3.99.3.2411.1239.4.9
Interim mitigation

Upgrade to Splunk Enterprise versions 10.2.0, 10.0.3, 9.4.9, 9.3.9 or later, or Splunk Cloud Platform versions 10.2.2510.4, 10.1.2507.15, 10.0.2503.11, 9.3.2411.123 or later.

Recommended fix High confidence

Splunk Enterprise: upgrade to 10.2.0 or later (or minimum 9.3.9/9.4.9/10.0.3 per branch); Splunk Cloud Platform: upgrade to 10.2.2510.4 or later via Splunk Support

  1. 1. Identify current Splunk Enterprise or Splunk Cloud Platform version by navigating to Settings > About > Version information
  2. 2. Review Splunk upgrade documentation at docs.splunk.com/DO NOT/Upgrade for pre-upgrade checklist and requirements
  3. 3. Create a full backup of Splunk configuration and data, including $SPLUNK_HOME/etc/ and any custom apps
  4. 4. For Splunk Enterprise: upgrade to version 9.3.9, 9.4.9, 10.0.3, or preferably 10.2.0 or later
  5. 5. For Splunk Cloud Platform: contact Splunk Support to request upgrade to version 9.3.2411.123, 10.0.2503.11, 10.1.2507.15, or preferably 10.2.2510.4 or later
  6. 6. After upgrade, verify the vulnerability is resolved by confirming the /manager/launcher/data/ui/views/_new endpoint properly sanitizes input
  7. 7. Test that legitimate View creation functions correctly post-upgrade
Caveat Review Splunk Upgrade Manual for potential breaking changes between major versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20162 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data