CVE Intelligence
High CSRF

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 Jul 15, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: cisco

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Splunk
Splunk and 2 more
CVSS base
8.3
High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Splunk Splunk, Splunk Splunk Cloud Platform, Splunk Splunk Enterprise).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (csrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Splunk Splunk ≥ 9.4.0 and < 9.4.13≥ 10.0.0 and < 10.0.8≥ 10.2.0 and < 10.2.5version 10.4.0 Vulnerable NIST National Vulnerability Database
Splunk Splunk Cloud Platform ≥ 10.1.2507 and < 10.1.2507.24≥ 10.4.2604 and < 10.4.2604.7≥ 10.3.2512 and < 10.3.2512.16≥ 10.2.2510 and < 10.2.2510.18 Vulnerable NIST National Vulnerability Database
Splunk Splunk Cloud Platform ≥ 10.1.2507 and < 10.1.2507.24≥ 10.2.2510 and < 10.2.2510.18≥ 10.3.2512 and < 10.3.2512.16≥ 10.4.2604 and < 10.4.2604.7≥ 10.5.2605 and < 10.5.2605.0 Vulnerable CVE Program (cve.org) e CISA ADP
Splunk Splunk Enterprise ≥ 10.4 and < 10.4.1≥ 9.4 and < 9.4.13≥ 10.0 and < 10.0.8≥ 10.2 and < 10.2.5 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.3 CVSS 3.1 High 2.8 5.5 psirt@cisco.com via NIST National Vulnerability Database
8.3 CVSS 3.1 High — — cisco via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L (score shown at the top: psirt@cisco.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-352 · Cross-Site Request Forgery (CSRF)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · splunk/splunk enterprise, splunk/splunk cloud platform
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 8.3
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Jul 15, 2026 · cisco

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

Elsewhere on this site

Splunk
every CVE for this vendor
CSRF
same class
CWE-352
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise 8d
  • CVE-2026-76284 Improper Neutralization in Splunk Enterprise 8d
  • CVE-2026-76279 Improper Input Validation of Index Names through the collect Command in Splunk Enterprise 8d
  • CVE-2026-76281 Improper Access Control in Splunk Enterprise 8d
  • CVE-2026-76280 Incorrect Permission Assignment for App Key Value Store Collections in Splunk Secure Gateway 8d
  • CVE-2026-76278 Authorization Bypass in SPL2 Module Permissions in Splunk Enterprise 8d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-20296 is "SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise", rated High. It affects Splunk (Splunk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.