Splunk Enterprise RCE Vulnerability Affects Cloud Platform

A critical remote code execution (RCE) vulnerability has been disclosed, impacting multiple versions of Splunk Enterprise and Splunk Cloud Platform.

Tracked as CVE-2026-20204, this high-severity flaw carries a CVSS score of 7.1 and poses a significant threat to organizational networks.

Discovered and reported by Splunk researcher Gabriel Nitu, the vulnerability allows attackers to perform Remote Code Execution (RCE) attacks.

Because Splunk often processes sensitive log data and security metrics, an RCE flaw in this environment requires immediate attention from system administrators.

Splunk Enterprise and Cloud Vulnerability

The root cause of this security issue lies in how the software manages temporary files. Categorized under CWE-377, the flaw involves the improper handling and insufficient isolation of specific files within the Splunk Web component.

When an application fails to isolate temporary data properly, it creates an opening for attackers to manipulate system processes.

To successfully exploit this specific weakness, an attacker only needs standard access. The attack chain relies on the following conditions:

• The threat actor must hold a low-privileged user account, meaning they do not need advanced admin or power roles to launch an attack.
• The attacker must upload a carefully crafted, malicious file directly into the SPLUNK_HOME/var/run/splunk/apptemp directory.
• Once the malicious file is uploaded and processed, the attacker can execute unauthorized code remotely on the host server.

Organizations must audit their current deployments to determine if they are running a vulnerable version. The issue impacts deployments where the Splunk Web component remains active.

For Splunk Enterprise environments, the vulnerability affects multiple distinct release branches. Specifically, it affects the 10.2 series before 10.2.1, the 10.0 series before 10.0.5, releases 9.4.0 through 9.4.9, and the 9.3 series up to 9.3.10.

Splunk Cloud Platform users also face exposure across several builds. The impacted cloud versions include releases below 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127.

Splunk has confirmed that the newer 10.4.2603 branch remains completely unaffected by this specific vulnerability.

Mitigations

According to Splunk’s official security advisory (SVD-2026-0403), organizations should implement immediate protective measures to prevent unauthorized exploitation.

The vendor currently notes no active detections of this flaw in the wild, giving administrators a vital window to secure their systems.

Security teams should apply the following solutions to mitigate the threat:

• Upgrade all Splunk Enterprise installations to the latest, secure versions, including 10.2.1, 10.0.5, 9.4.10, 9.3.11, or higher.
• Monitor Splunk Cloud Platform instances, as the vendor is actively rolling out patches to these environments automatically.
• Temporarily turn off the Splunk Web component.
• Modify the web configuration file to turn off the web interface, effectively blocking the attack path until permanent patches are applied.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.