CVE-2026-20240Splunk Splunk Improper Input Validation
NVDCVSS scored by psirt@cisco.com
Vulnerability Summary
In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, and Splunk Cloud Platform versions below 10.4.2603.1, 10.3.2512.9, 10.2.2510.11, 10.1.2507.21, 10.0.2503.13, and 9.3.2411.129, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause a Denial of Service by exploiting the `coldToFrozen.sh` script in the `splunk_archiver` app to rename critical Splunk directories, making the instance non-functional.<br><br>The Denial of Service is possible because of missing input validation in the `coldToFrozen.sh` script, which accepts arbitrary file paths and renames them without restricting operations to safe directories.
CVSS v3.1 Base Metrics — Score 6.5 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
Affected & Patched Versions
- Splunk Splunk >= 9.3.0 and < 9.3.12
- Splunk Splunk >= 9.4.0 and < 9.4.11
- Splunk Splunk >= 10.0.0 and < 10.0.5
- Splunk Splunk >= 10.2.0 and < 10.2.2
- Splunk Splunk Cloud Platform >= 9.3.2411 and < 9.3.2411.129
- Splunk Splunk Cloud Platform >= 10.0.2503 and < 10.0.2503.13
- Splunk Splunk Cloud Platform >= 10.1.2507 and < 10.1.2507.21
- Splunk Splunk Cloud Platform >= 10.2.2510 and < 10.2.2510.11
- Splunk Splunk Cloud Platform >= 10.3.2512 and < 10.3.2512.9
- Splunk Splunk Cloud Platform
- Splunk Enterprise >= 10.2 and < 10.2.2
- Splunk Enterprise >= 10.0 and < 10.0.5
- Splunk Enterprise >= 9.4 and < 9.4.11
- Splunk Enterprise >= 9.3 and < 9.3.12
- Splunk Cloud Platform >= 10.4.2603 and < 10.4.2603.1
- Splunk Cloud Platform >= 10.3.2512 and < 10.3.2512.9
- Splunk Cloud Platform >= 10.2.2510 and < 10.2.2510.11
- Splunk Cloud Platform >= 10.1.2507 and < 10.1.2507.21
- Splunk Cloud Platform >= 10.0.2503 and < 10.0.2503.13
- Splunk Cloud Platform >= 9.3.2411 and < 9.3.2411.129
- Splunk Splunk 9.3.12
- Splunk Splunk 9.4.11
- Splunk Splunk 10.0.5
- Splunk Splunk 10.2.2
- Splunk Splunk Cloud Platform 9.3.2411.129
- Splunk Splunk Cloud Platform 10.0.2503.13
- Splunk Splunk Cloud Platform 10.1.2507.21
- Splunk Splunk Cloud Platform 10.2.2510.11
- Splunk Splunk Cloud Platform 10.3.2512.9
- Splunk Enterprise 10.2.2
- Splunk Enterprise 10.0.5
- Splunk Enterprise 9.4.11
- Splunk Enterprise 9.3.12
- Splunk Cloud Platform 10.4.2603.1
- Splunk Cloud Platform 10.3.2512.9
- Splunk Cloud Platform 10.2.2510.11
- Splunk Cloud Platform 10.1.2507.21
- Splunk Cloud Platform 10.0.2503.13
- Splunk Cloud Platform 9.3.2411.129
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Splunk Splunk and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- May 20, 2026Published
- Jul 23, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Splunk Splunk CVEsYou are reading CVE-2026-20240. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
- Vendor Advisoryhttps://advisory.splunk.com/advisories/SVD-2026-0504
Data last checked: Nov 22, 2026 17:11 UTC