CVE-2026-20204 is a high-severity remote code execution vulnerability affecting Splunk Enterprise and Splunk Cloud Platform. The flaw is caused by improper handling and insufficient isolation of temporary files within Splunk’s application temporary directory. A low-privileged authenticated Splunk user who does not hold the admin or power roles can upload a malicious file into the apptemp area, where it may be processed in a manner that results in code execution on the underlying host. The issue is associated with insecure temporary file handling in the Splunk Web attack surface and affects Splunk Enterprise versions earlier than 10.2.1, 10.0.5, 9.4.10, and 9.3.11, as well as Splunk Cloud Platform versions earlier than 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity remote code execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by improper handling of temporary files and insufficient isolation in the apptemp directory, allowing low-privileged users to upload a malicious file and execute code.
A high-severity vulnerability in Splunk Enterprise and Splunk Cloud Platform involving improper handling and isolation of temporary files that allows a low-privileged remote attacker to upload files to /var/run/splunk/apptemp, potentially leading to remote code execution.
A high-severity remote code execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by improper handling and insufficient isolation of temporary files in the Splunk Web component.
A remote code execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by insecure handling of temporary files in the apptemp directory, allowing a low-privileged authenticated user to upload a malicious file that gets processed or executed when Splunk Web is enabled.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.