CVE-2026-20296

SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise

HIGH
8.3
CVSS Score
Published: July 15, 2026 at 05:18 PM UTC
Updated: July 24, 2026 at 06:30 PM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.0.810.0.0 ≤ v < 10.0.810.2 ≤ v < 10.2.510.2.0 ≤ v < 10.2.510.4 ≤ v < 10.4.19.4 ≤ v < 9.4.139.4.0 ≤ v < 9.4.1310.010.210.410.4.09.4
Affected range stops below 10.0.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.13, so it looks safe — our inference, not a vendor statement
v < 10.5.2605.010.1.2507 ≤ v < 10.1.2507.2410.2.2510 ≤ v < 10.2.2510.1810.3.2512 ≤ v < 10.3.2512.1610.4.2604 ≤ v < 10.4.2604.710.1.250710.2.251010.3.251210.4.260410.5.2605
Affected range stops below 10.1.2507.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2510.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.3.2512.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.2604.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.5.2605.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.3HIGHcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card