cve.bz

CVE-2026-20296 splunk: Cross Site Reference Forgery

8.3 highEPSS 0.2%

High (8.3) in splunk. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-20296 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-20296?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-20296?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-20296 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Splunk Enterprisefrom 10.4 before 10.4.1
Splunk Enterprisefrom 10.2 before 10.2.5
Splunk Enterprisefrom 10.0 before 10.0.8
Splunk Enterprisefrom 9.4 before 9.4.13
Splunk Cloud Platformfrom 10.5.2605 before 10.5.2605.0
Splunk Cloud Platformfrom 10.4.2604 before 10.4.2604.7
Splunk Cloud Platformfrom 10.3.2512 before 10.3.2512.16
Splunk Cloud Platformfrom 10.2.2510 before 10.2.2510.18
Splunk Cloud Platformfrom 10.1.2507 before 10.1.2507.24

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON