CVE-2026-20163: Splunk Enterprise · The software constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 8.0 High · fixed in 10.0.4 : patch Splunk Enterprise soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.0.4, 9.4.9, 9.3.10 +4
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation 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 30 Oct 2026.
What to do
Upgrade Splunk to 10.0.4, 9.4.9 or 9.3.10 (Enterprise); 10.2.2510.5, 10.1.2507.16, 10.0.2503.12 or 9.3.2411.124 (Cloud Platform).
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Cloud Platform | Affected
| Fixed in
|
| SplunkSplunk Cloud Platform | Affected
| Fixed in
|
| SplunkSplunk Cloud Platform | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-20163, organizations should immediately upgrade affected Splunk Enterprise and Splunk Cloud Platform instances to the fixed versions specified by Splunk. If immediate patching is not feasible, restrict the assignment of the 'edit_cmd' capability to only the most trusted administrators and monitor usage of the /splunkd/__upload/indexing/preview REST endpoint for anomalous activity. Implement strict access controls and multi-factor authentication for Splunk administrative roles to reduce risk of credential compromise. Additionally, audit and review Splunk role assignments regularly to ensure least privilege principles are enforced. Network segmentation and monitoring of Splunk server traffic can help detect and contain potential exploitation attempts. Finally, maintain comprehensive logging and alerting on Splunk server activities to enable rapid detection and response to suspicious command executions.
Description
In Splunk Enterprise versions below 10.2.0, 10.0.4, 9.4.9, and 9.3.10, and Splunk Cloud Platform versions below 10.2.2510.5, 10.0.2503.12, 10.1.2507.16, and 9.3.2411.124, a user who holds a role that contains the high-privilege capability `edit_cmd` could execute arbitrary shell commands using the `unarchive_cmd` parameter for the `/splunkd/__upload/indexing/preview` REST endpoint.