Skip to main content
VulnerabilityPublished

CVE-2026-20240: Splunk Enterprise · The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High · fixed in 10.2.2 : patch Splunk Enterprise soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.2.2, 10.0.5, 9.4.11 +7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.2
Fixed in
  • 10.2.2
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.5
Fixed in
  • 10.0.5
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.11
Fixed in
  • 9.4.11
SplunkSplunk EnterpriseAffected
  • >=9.3 <9.3.12
Fixed in
  • 9.3.12
SplunkSplunk Cloud PlatformAffected
  • >=10.4.2603 <10.4.2603.1
Fixed in
  • 10.4.2603.1
SplunkSplunk Cloud PlatformAffected
  • >=10.3.2512 <10.3.2512.9
Fixed in
  • 10.3.2512.9

AI-suggested

If you cannot patch yet, restrict access to the splunk_archiver app and the coldToFrozen.sh script to trusted users only, and monitor for any unauthorized attempts to execute this script. Avoid granting low-privileged users access to this functionality. Follow official Splunk advisories for updates.

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.

References

Community reviews

Loading reviews…