CVE-2026-20204: Creating and using insecure temporary files can leave application and system data vulnerable to attack. in Splunk Splunk Enterprise
In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127, a low-privileged user that does not hold the `admin` or `power` Splunk roles could potentially perform a Remote Code Execution (RCE) by uploading a malicious file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory due to improper handling and insufficient isolation of temporary files within the `apptemp` directory.
AI Analysis
Technical Summary
This vulnerability in Splunk Enterprise arises from improper handling and insufficient isolation of temporary files in the $SPLUNK_HOME/var/run/splunk/apptemp directory. A low-privileged user lacking admin or power roles can upload a malicious file to this directory, potentially leading to remote code execution. Affected versions include those below 10.2.1, 10.0.5, 9.4.10, and 9.3.11. The CVSS 3.1 score of 7.1 reflects a network attack vector with high impact on confidentiality, integrity, and availability, though requiring high attack complexity and user interaction.
Potential Impact
Successful exploitation could allow an attacker with limited Splunk privileges to execute arbitrary code remotely, potentially compromising system and application data confidentiality, integrity, and availability. This elevates the risk profile of affected Splunk Enterprise deployments by enabling privilege escalation and remote control.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the apptemp directory and limit user roles to trusted personnel only. Monitor for unusual file uploads in the apptemp directory and consider applying compensating controls to isolate temporary file handling.
CVE-2026-20204: Creating and using insecure temporary files can leave application and system data vulnerable to attack. in Splunk Splunk Enterprise
Description
In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, and 9.3.2411.127, a low-privileged user that does not hold the `admin` or `power` Splunk roles could potentially perform a Remote Code Execution (RCE) by uploading a malicious file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory due to improper handling and insufficient isolation of temporary files within the `apptemp` directory.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Splunk Enterprise arises from improper handling and insufficient isolation of temporary files in the $SPLUNK_HOME/var/run/splunk/apptemp directory. A low-privileged user lacking admin or power roles can upload a malicious file to this directory, potentially leading to remote code execution. Affected versions include those below 10.2.1, 10.0.5, 9.4.10, and 9.3.11. The CVSS 3.1 score of 7.1 reflects a network attack vector with high impact on confidentiality, integrity, and availability, though requiring high attack complexity and user interaction.
Potential Impact
Successful exploitation could allow an attacker with limited Splunk privileges to execute arbitrary code remotely, potentially compromising system and application data confidentiality, integrity, and availability. This elevates the risk profile of affected Splunk Enterprise deployments by enabling privilege escalation and remote control.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the apptemp directory and limit user roles to trusted personnel only. Monitor for unusual file uploads in the apptemp directory and consider applying compensating controls to isolate temporary file handling.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- cisco
- Date Reserved
- 2025-10-08T11:59:15.397Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69dfaf6882d89c981f612b75
Added to database: 4/15/2026, 3:31:52 PM
Last enriched: 4/15/2026, 3:46:55 PM
Last updated: 4/16/2026, 5:51:10 AM
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.