Splunk Enterprise: Server-Side Request Forgery
CVE-2026-20252 is a high-severity server-side request forgery vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 10.2.4, 10.0.7, 9.4.12 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.35% 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.2.4 or 10.0.7 or 9.4.12 or 9.3.13, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 10.4.2604.3 or 10.3.2512.12 or 10.2.2510.14 or 10.1.2507.22, whichever matches your release line, or a later version.
- Update Splunk to 9.3.13 or 9.4.12 or 10.0.7 or 10.2.4, whichever matches your release line, or a later version.
- Read the advisory on advisory.splunk.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Splunk | Splunk Enterprise | 10.2 up to, but not including, 10.2.4; 10.0 up to, but not including, 10.0.7; 9.4 up to, but not including, 9.4.12; 9.3 up to, but not including, 9.3.13 | 10.2.4, 10.0.7, 9.4.12, 9.3.13 |
| Splunk | Splunk Cloud Platform | 10.4.2604 up to, but not including, 10.4.2604.3; 10.3.2512 up to, but not including, 10.3.2512.12; 10.2.2510 up to, but not including, 10.2.2510.14; 10.1.2507 up to, but not including, 10.1.2507.22; 9.3.2411 up to, but not including, 9.3.2411.132 | 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, 9.3.2411.132 |
| Splunk | Splunk | 9.3.0 up to, but not including, 9.3.13; 9.4.0 up to, but not including, 9.4.12; 10.0.0 up to, but not including, 10.0.7; 10.2.0 up to, but not including, 10.2.4 | 9.3.13, 9.4.12, 10.0.7, 10.2.4 |
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
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L. Scored by CNA (cisco.com).
Official description
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature. The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Server-Side Request Forgery
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
How developers prevent this class of flaw
- If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
- If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- 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 Server-Side Request Forgery vulnerabilities
- 8.6 High severity
- 10.0 Critical severity
- 7.3 High severity
- 7.1 High severity
- 7.2 High severity
- 9.9 Critical severity
Spotted an error? Tell us.