Splunk Enterprise: Cross-Site Request Forgery
CVE-2026-20296 is a high-severity cross-site request forgery vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 10.4.1, 10.2.5, 10.0.8 as the first without the flaw, so updating Splunk Enterprise to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Splunk Enterprise to 10.4.1 or 10.2.5 or 10.0.8 or 9.4.13, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 10.5.2605.0 or 10.4.2604.7 or 10.3.2512.16 or 10.2.2510.18, whichever matches your release line, or a later version.
- Update Splunk to 9.4.13 or 10.0.8 or 10.2.5, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 up to, but not including, 10.4.1; 10.2 up to, but not including, 10.2.5; 10.0 up to, but not including, 10.0.8; 9.4 up to, but not including, 9.4.13 | 10.4.1, 10.2.5, 10.0.8, 9.4.13 |
| Splunk | Splunk Cloud Platform | 10.5.2605 up to, but not including, 10.5.2605.0; 10.4.2604 up to, but not including, 10.4.2604.7; 10.3.2512 up to, but not including, 10.3.2512.16; 10.2.2510 up to, but not including, 10.2.2510.18; 10.1.2507 up to, but not including, 10.1.2507.24 | 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, 10.1.2507.24 |
| Splunk | Splunk | 9.4.0 up to, but not including, 9.4.13; 10.0.0 up to, but not including, 10.0.8; 10.2.0 up to, but not including, 10.2.5; 10.4.0 | 9.4.13, 10.0.8, 10.2.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. Scored by CNA (cisco.com).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cross-Site Request Forgery
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, use anti-CSRF packages such as the OWASP CSRFGuard. Another example is the ESAPI Session Management control, which includes a component for CSRF.
- Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Splunk Enterprise
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 9.9 Critical severity
- 8.8 High severity
- 7.2 High severity
Recent Cross-Site Request Forgery vulnerabilities
- 8.3 High severity
- 8.1 High severity
- 7.1 High severity
- 8.8 High severity
- 8.1 High severity
- 8.8 High severity
Spotted an error? Tell us.