Skip to main content
Mallory
HighVulnerability

CVE-2026-20163: Command Injection in Splunk upload preview endpoint

Published Mar 11, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3.1
EPSS0.54%46th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Splunk
IdentifiersCVE-2026-20163CWE-77 · Improper Neutralization of Special…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication
FAQ

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.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
zeropath blogNews · Jun 17, 2026Brief Summary: CVE-2026-20266 OS Command Injection in Splunk AI Toolkit btool Configuration Helper - ZeroPath Blog | ZeroPathA prior Splunk command injection vulnerability on the /splunkd/__upload/indexing/preview endpoint, referenced as a parallel example sharing the same CWE-78 weakness.Read more ↗zeropath blogNews · Jun 10, 2026Quick Look: Splunk Secure Gateway CVE-2026-20251 RCE via jsonpickle Deserialization - ZeroPath Blog | ZeroPathA closely related Splunk Enterprise and Cloud Platform remote code execution vulnerability using the same jsonpickle/KV Store deserialization mechanism, but requiring admin-level privileges and confirmed exploited in the wild.Read more ↗cyber security newsNews · Mar 12, 2026Splunk RCE Vulnerability Allows Attackers to Execute Arbitrary Shell CommandsA high-severity remote command execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by improper sanitization of user-controlled input (CWE-77) in the file upload preview/indexing REST API endpoint, enabling arbitrary shell command execution when a user has the high-privilege edit_cmd capability.Read more ↗sdxcentral cybersecurityNews · Oct 30, 2025Splunk suite at threat from remote code execution - SDxCentralA remote command execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by insufficient input sanitization in the upload preview interface's unarchive option, allowing arbitrary shell commands on the host OS.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.