Cyber Resilience

CVE-2026-20296

CSRF in Splunk 9.4.0 – 9.4.13

Published
15 July 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
EPSS Score 0.0023 14th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-20296 is a high-severity CSRF (CWE-352) vulnerability in Splunk Splunk. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

CSRF + input injection in Splunk Web directly enables exploitation of the public-facing application to execute privileged SPL searches.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-20321Same product: Splunk Splunk
CVE-2025-20228Same product: Splunk Splunk
CVE-2025-20322Same product: Splunk Splunk
CVE-2024-45737Same product: Splunk Splunk
CVE-2023-22942Same product: Splunk Splunk
CVE-2024-39019Shared CWE-352
CVE-2025-23573Shared CWE-352
CVE-2024-28678Shared CWE-352
CVE-2024-37093Shared CWE-352
CVE-2025-9634Shared CWE-352

Affected Assets

splunk
splunk
10.4.0 · 9.4.0 — 9.4.13 · 10.0.0 — 10.0.8 · 10.2.0 — 10.2.5
splunk
splunk cloud platform
10.1.2507 — 10.1.2507.24 · 10.2.2510 — 10.2.2510.18 · 10.3.2512 — 10.3.2512.16

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-23 Session Authenticity
  • AC-3 Access Enforcement
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires protection of session authenticity, which would block the CSRF token omission on GET requests that allows forged SPL execution.

prevent

Enforces that only properly authenticated and authorized requests (including CSRF validation) can invoke Deployment Server endpoints or run SPL as splunk-system-user.

prevent

Requires validation and neutralization of caller-supplied input before it is used in SPL searches, preventing the arbitrary search execution described in the CVE.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References