CVE intelligence and bounded remediation
CVE-2026-20162 — Splunk Splunk security vulnerability
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.
- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Published
- 2026-03-11
- CISA KEV
- Not currently listed
- Ecosystem
- javascript/npm
- Weaknesses
- CWE-79
Affected products
- splunk / splunk
- splunk / splunk_cloud_platform
Showing 2 representative product identities from 7 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.
Matched remediation archetype
Cross-site scripting and unsafe browser output
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
- Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
- Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.
Remediate safely
- Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
- Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
- Update affected rendering components and add tests for every output context using inert sentinel markup.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.