CVE-2026-20204

Improper Handling and Insufficient Isolation of Specific Temporary Files in Splunk Enterprise

HIGH
7.1
CVSS Score
Published: April 15, 2026 at 03:17 PM UTC
Updated: October 26, 2026 at 09:10 PM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 3%
SSVC
No known exploit

Description

In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 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, a low-privileged user that does not hold the `admin` or `power` Splunk roles could potentially perform a Remote Code Execution (RCE) by uploading a malicious file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory due to improper handling and insufficient isolation of temporary files within the `apptemp` directory.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0.0 ≤ v < 10.0.59.3.0 ≤ v < 9.3.119.4.0 ≤ v < 9.4.1010.010.210.2.09.39.4
Affected range stops below 10.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.10, so it looks safe — our inference, not a vendor statement
10.0.2503 ≤ v < 10.0.2503.1310.1.2507 ≤ v < 10.1.2507.1910.2.2510 ≤ v < 10.2.2510.910.3.2512 ≤ v < 10.3.2512.59.3.2411 ≤ v < 9.3.2411.12710.0.250310.1.250710.2.251010.3.251210.4.26039.3.2411
Affected range stops below 10.0.2503.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.2507.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2510.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.3.2512.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.127, so it looks safe — our inference, not a vendor statement
Affected range stops below Not Affected, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-377

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card