CVE-2026-20297
7.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Summary
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, and 10.1.2507.24, a user who holds a role that contains the edit_local_apps and install_apps capabilities could cause a legitimate app installation to write files outside the intended app directory, into $SPLUNK_HOME/etc/ and its subdirectories.<br><br>The vulnerability is caused by a path traversal in the app installation workflow, which does not restrict the installation path to the intended app directory.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 < 10.4.1 | affected |
| Splunk | Splunk Enterprise | 10.2 < 10.2.5 | affected |
| Splunk | Splunk Enterprise | 10.0 < 10.0.8 | affected |
| Splunk | Splunk Enterprise | 9.4 < 9.4.13 | affected |
| Splunk | Splunk Enterprise | 9.3 < 9.3.14 | affected |
| Splunk | Splunk Cloud Platform | 10.5.2605 < 10.5.2605.0 | affected |
| Splunk | Splunk Cloud Platform | 10.4.2604 < 10.4.2604.6 | affected |
| Splunk | Splunk Cloud Platform | 10.2.2510 < 10.2.2510.18 | affected |
| Splunk | Splunk Cloud Platform | 10.1.2507 < 10.1.2507.24 | affected |
Weaknesses
- CWE-22: The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: no
- Technical Impact: total
References
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.