Splunk Enterprise and Cloud Platform
CVE-2026-20296: 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.
Published
Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.
Affected and fixed versions
| Product / branch | Fixed in |
|---|---|
| Splunk Enterprise 10.4 | 10.4.1 or later |
| Splunk Enterprise 10.2 | 10.2.5 or later |
| Splunk Enterprise 10.0 | 10.0.8 or later |
| Splunk Enterprise 9.4 | 9.4.13 or later |
| Splunk Cloud Platform 10.5 | 10.5.2605.0 or later |
| Splunk Cloud Platform 10.4 | 10.4.2604.7 or later |
| Splunk Cloud Platform 10.3 | 10.3.2512.16 or later |
| Splunk Cloud Platform 10.2 | 10.2.2510.18 or later |
| Splunk Cloud Platform 10.1 | 10.1.2507.24 or later |
Always confirm against the vendor advisory, which lists every fixed hotfix.
What it is
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.
Sources
KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.