SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise
Summary
| CVE | CVE-2026-20296 |
|---|---|
| State | PUBLISHED |
| Assigner | cisco |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-15 18:16:44 UTC |
| Updated | 2026-07-16 05:16:18 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 8.3 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
EPSS: 0.001700000 probability, percentile 0.066870000 (date 2026-07-20)
Problem Types: CWE-352 | CWE-352 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.
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 8.3 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
| 3.1 | CNA | CVSS | 8.3 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
RequiredScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
LowCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Splunk | Splunk Enterprise | affected 10.4 10.4.1 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 10.2 10.2.5 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 10.0 10.0.8 custom | Not specified |
| CNA | Splunk | Splunk Enterprise | affected 9.4 9.4.13 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.5.2605 10.5.2605.0 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.4.2604 10.4.2604.7 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.3.2512 10.3.2512.16 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.2.2510 10.2.2510.18 custom | Not specified |
| CNA | Splunk | Splunk Cloud Platform | affected 10.1.2507 10.1.2507.24 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| advisory.splunk.com/advisories/SVD-2026-0702 | [email protected] | advisory.splunk.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.