CVE-2026-20163: Command Injection in Splunk upload preview endpoint
- Vendor
- Splunk
CVE-2026-20163 is a remote command execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by insufficient neutralization of user-controlled input in the upload preview workflow prior to indexing. The vulnerable functionality resides in the REST API endpoint used for indexing preview, where the unarchive_cmd parameter can be influenced by an authenticated user whose role includes the high-privilege edit_cmd capability. Because the parameter is not properly sanitized before being passed to shell-interpreted functionality, an attacker can inject arbitrary shell commands and cause them to execute on the underlying host operating system. Affected versions include Splunk Enterprise releases prior to 10.2.0, 10.0.4, 9.4.9, and 9.3.10, and Splunk Cloud Platform releases prior to 10.2.2510.5, 10.1.2507.16, 10.0.2503.12, and 9.3.2411.124.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary shell command execution on the host running the affected Splunk instance. This can result in full compromise of the Splunk server in the security context of the Splunk service, including unauthorized access to indexed data, modification of Splunk content and configurations, disruption of monitoring operations, installation of persistence mechanisms, and potential lateral movement to other reachable systems.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, remove the edit_cmd capability from all roles that do not strictly require it. Restrict access to the affected upload preview functionality to the smallest possible set of trusted administrative users and review role assignments for unnecessary high-privilege capabilities. Because no specific detection signatures are noted as available, compensating controls should focus on privilege reduction and rapid patch deployment.
Remediation
Patch, then assume compromise.
Upgrade Splunk Enterprise to a fixed release: 10.2.0 or later, 10.0.4 or later, 9.4.9 or later, or 9.3.10 or later, depending on the deployed branch. For Splunk Cloud Platform, apply the vendor-provided fixed builds or ensure the service has been updated to 10.2.2510.5, 10.1.2507.16, 10.0.2503.12, 9.3.2411.124, or later as applicable. Splunk Cloud instances should be updated through the vendor-managed patching process.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-20163 exploited in the wild?
- Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-20163?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-20163.
- Is there a patch for CVE-2026-20163?
- Upgrade Splunk Enterprise to a fixed release: 10.2.0 or later, 10.0.4 or later, 9.4.9 or later, or 9.3.10 or later, depending on the deployed branch. For Splunk Cloud Platform, apply the vendor-provided fixed builds or ensure the service has been updated to 10.2.2510.5, 10.1.2507.16, 10.0.2503.12, 9.3.2411.124, or later as applicable.
- What products are affected by CVE-2026-20163?
- Splunk and Splunk Cloud Platform.
- How severe is CVE-2026-20163?
- CVE-2026-20163 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 0.54% (46th percentile) as of Sep 25, 2026.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.