Splunk Enterprise: Improper Access Control
CVE-2025-20229 is a high-severity improper access control vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.0 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 9.4.0, 9.3.3, 9.2.5 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 16% chance of exploitation within 30 days, which is in the top 3.03% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Splunk Enterprise to 9.4.0 or 9.3.3 or 9.2.5 or 9.1.8, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 9.3.2408.104 or 9.2.2406.108 or 9.2.2403.114 or 9.1.2312.208, whichever matches your release line, or a later version.
- Update Splunk to 9.1.8 or 9.2.5 or 9.3.3, 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 | 9.4 up to, but not including, 9.4.0; 9.3 up to, but not including, 9.3.3; 9.2 up to, but not including, 9.2.5; 9.1 up to, but not including, 9.1.8 | 9.4.0, 9.3.3, 9.2.5, 9.1.8 |
| Splunk | Splunk Cloud Platform | 9.3.2408 up to, but not including, 9.3.2408.104; 9.2.2406 up to, but not including, 9.2.2406.108; 9.2.2403 up to, but not including, 9.2.2403.114; 9.1.2312 up to, but not including, 9.1.2312.208 | 9.3.2408.104, 9.2.2406.108, 9.2.2403.114, 9.1.2312.208 |
| Splunk | Splunk | 9.1.0 up to, but not including, 9.1.8; 9.2.0 up to, but not including, 9.2.5; 9.3.0 up to, but not including, 9.3.3; 9.4.0 | 9.1.8, 9.2.5, 9.3.3 |
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
- LowNo special conditions are needed; the attack works reliably.
- 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:L/PR:L/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official description
In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8, and Splunk Cloud Platform versions below 9.3.2408.104, 9.2.2406.108, 9.2.2403.114, and 9.1.2312.208, a low-privileged user that does not hold the "admin" or "power" Splunk roles could perform a Remote Code Execution (RCE) through a file upload to the "$SPLUNK_HOME/var/run/splunk/apptemp" directory due to missing authorization checks.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
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
Recent Improper Access Control vulnerabilities
- 7.3 High severity
- 7.5 High severity
- 7.5 High severity
- 7.3 High severity
- 8.1 High severity
- 7.5 High severity
Spotted an error? Tell us.