In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud…
CVE-2026-20204 is a high-severity vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists versions 10.2.1, 10.0.5, 9.4.10 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.15% chance of exploitation within 30 days, higher than 88% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 10.2.1 or 10.0.5 or 9.4.10 or 9.3.11, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to Not Affected or 10.3.2512.5 or 10.2.2510.9 or 10.1.2507.19, whichever matches your release line, or a later version.
- Update Splunk to 9.3.11 or 9.4.10 or 10.0.5, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.2 up to, but not including, 10.2.1; 10.0 up to, but not including, 10.0.5; 9.4 up to, but not including, 9.4.10; 9.3 up to, but not including, 9.3.11 | 10.2.1, 10.0.5, 9.4.10, 9.3.11 |
| Splunk | Splunk Cloud Platform | 10.4.2603 up to, but not including, Not Affected; 10.3.2512 up to, but not including, 10.3.2512.5; 10.2.2510 up to, but not including, 10.2.2510.9; 10.1.2507 up to, but not including, 10.1.2507.19; 10.0.2503 up to, but not including, 10.0.2503.13; 9.3.2411 up to, but not including, 9.3.2411.127 | Not Affected, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, 9.3.2411.127 |
| Splunk | Splunk | 9.3.0 up to, but not including, 9.3.11; 9.4.0 up to, but not including, 9.4.10; 10.0.0 up to, but not including, 10.0.5; 10.2.0 | 9.3.11, 9.4.10, 10.0.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Spotted an error? Tell us.