vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-20240

Denial of Service through coldToFrozen.sh Script in Splunk Enterprise

MEDIUM
6.5
CVSS Score
Published: May 20, 2026 at 04:32 PM UTC
Updated: July 23, 2026 at 07:31 PM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Splunk· Splunk
95%
10.0 ≤ v < 10.0.510.0.0 ≤ v < 10.0.510.2 ≤ v < 10.2.210.2.0 ≤ v < 10.2.29.3 ≤ v < 9.3.129.3.0 ≤ v < 9.3.129.4 ≤ v < 9.4.119.4.0 ≤ v < 9.4.1110.010.29.39.4
Affected range stops below 10.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.11, so it looks safe — our inference, not a vendor statement
Splunk Cloud Platform· Splunk
95%
10.0.2503 ≤ v < 10.0.2503.1310.1.2507 ≤ v < 10.1.2507.2110.2.2510 ≤ v < 10.2.2510.1110.3.2512 ≤ v < 10.3.2512.910.4.2603 ≤ v < 10.4.2603.19.3.2411 ≤ v < 9.3.2411.12910.0.250310.1.250710.2.251010.3.251210.4.26039.3.2411
Affected range stops below 10.0.2503.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.2507.21, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2510.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.3.2512.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.2603.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.129, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://advisory.splunk.com/advisories/SVD-2026-0504

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUM[email protected]
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card