Splunk Enterprise: Path Traversal: '.../...//'
CVE-2025-20320 is a high-severity path traversal: '.../...//' vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.3 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.3, 9.3.5, 9.2.7 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 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 9.4.3 or 9.3.5 or 9.2.7 or 9.1.10, whichever matches your release line, or a later version.
- Update Splunk Enterprise Cloud to 9.3.2411.107 or 9.3.2408.117 or 9.2.2406.121, whichever matches your release line, or a later version.
- Update Splunk to 9.1.10 or 9.2.7 or 9.3.5 or 9.4.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.3; 9.3 up to, but not including, 9.3.5; 9.2 up to, but not including, 9.2.7; 9.1 up to, but not including, 9.1.10 | 9.4.3, 9.3.5, 9.2.7, 9.1.10 |
| Splunk | Splunk Enterprise Cloud | 9.3.2411 up to, but not including, 9.3.2411.107; 9.3.2408 up to, but not including, 9.3.2408.117; 9.2.2406 up to, but not including, 9.2.2406.121 | 9.3.2411.107, 9.3.2408.117, 9.2.2406.121 |
| Splunk | Splunk | 9.1.0 up to, but not including, 9.1.10; 9.2.0 up to, but not including, 9.2.7; 9.3.0 up to, but not including, 9.3.5; 9.4.0 up to, but not including, 9.4.3 | 9.1.10, 9.2.7, 9.3.5, 9.4.3 |
| Splunk | Splunk Cloud Platform | 9.2.2406 up to, but not including, 9.2.2406.121; 9.3.2408 up to, but not including, 9.3.2408.117; 9.3.2411 up to, but not including, 9.3.2411.107 | 9.2.2406.121, 9.3.2408.117, 9.3.2411.107 |
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
- NoneNo data is disclosed.
- 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:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.3 | Medium | CNA (cisco.com) |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7 and 9.1.10, and Splunk Cloud Platform versions below 9.3.2411.107, 9.3.2408.117, and 9.2.2406.121, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the `User Interface - Views` configuration page that could potentially lead to a denial of service (DoS).The user could cause the DoS by exploiting a path traversal vulnerability that allows for deletion of arbitrary files within a Splunk directory. The vulnerability requires the low-privileged user to phish the administrator-level victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Path Traversal: '.../...//'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- 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 Path Traversal: '.../...//' vulnerabilities
- 7.5 High severity
- 8.1 High severity
- 8.1 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.