CVE-2025-20229 is a remote code execution vulnerability in Splunk Enterprise and Splunk Cloud Platform caused by missing authorization checks on a file upload path associated with the temporary application directory. In affected versions, a low-privileged authenticated user who does not have the admin or power role can upload a crafted file into Splunk’s application temporary area under apptemp and leverage that upload to achieve code execution. The flaw stems from insufficient authorization enforcement around access to functionality that should be restricted to higher-privileged roles, allowing an attacker to cross privilege boundaries and reach code-execution behavior through the upload and subsequent processing of attacker-controlled content.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior Splunk remote code execution vulnerability affecting the same apptemp directory attack surface, allowing a low-privileged authenticated user to achieve code execution via file upload.
A high-severity authorization validation flaw in Splunk Enterprise and Splunk Cloud Platform that can allow an authenticated remote attacker to upload a crafted file and achieve remote code execution.
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.