Splunk EE <=10.4.1: Deployment Server CSRF GET Grants Arbitrary SPL
CVE-2026-20296 Published on July 15, 2026
SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, and 10.1.2507.24, an attacker could trick a user that holds a role with the `list_deployment_server` capability into running arbitrary Search Processing Language (SPL) searches on their behalf as `splunk-system-user`, allowing for access to stored credentials and indexed data.<br><br>The vulnerability is possible because Deployment Server endpoints in Splunk Web do not validate Cross-Site Request Forgery (CSRF) tokens on GET requests, and caller-supplied input is not correctly neutralized before it is placed into an SPL search.
Weakness Type
What is a Session Riding Vulnerability?
The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. When a web server is designed to receive a request from a client without any mechanism for verifying that it was intentionally sent, then it might be possible for an attacker to trick a client into making an unintentional request to the web server which will be treated as an authentic request. This can be done via a URL, image load, XMLHttpRequest, etc. and can result in exposure of data or unintended code execution.
CVE-2026-20296 has been classified to as a Session Riding vulnerability or weakness.
Products Associated with CVE-2026-20296
stack.watch emails you whenever new vulnerabilities are published in Splunk or Splunk Cloud Platform. Just hit a watch button to start following.
Affected Versions
Splunk Enterprise:- Version 10.4 and below 10.4.1 is affected.
- Version 10.2 and below 10.2.5 is affected.
- Version 10.0 and below 10.0.8 is affected.
- Version 9.4 and below 9.4.13 is affected.
- Version 10.5.2605 and below 10.5.2605.0 is affected.
- Version 10.4.2604 and below 10.4.2604.7 is affected.
- Version 10.3.2512 and below 10.3.2512.16 is affected.
- Version 10.2.2510 and below 10.2.2510.18 is affected.
- Version 10.1.2507 and below 10.1.2507.24 is affected.