Loading vulnerability…
CVE-2026-20297 is a high-severity path traversal vulnerability in the App Install REST endpoint of Splunk Enterprise and Splunk Cloud Platform. The flaw is associated with the app installation workflow, specifically handling of the explicit_appname parameter, which does not properly constrain file writes to the intended application directory during a legitimate app installation. As a result, an authenticated user whose role includes both the edit_local_apps and install_apps capabilities can cause installation output to be written outside the target app directory and into Splunk configuration areas under $SPLUNK_HOME/etc/ and its subdirectories. This creates a privileged arbitrary file write condition within the Splunk application environment that can affect application configuration and other sensitive Splunk-managed files.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity path traversal vulnerability in Splunk products that could allow attackers to write files outside the intended application directory.
A high-severity path traversal vulnerability in Splunk's App Install REST endpoint that can allow authorized users to write files outside the intended application directory into sensitive Splunk directories.
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.