Splunk Enterprise: Server-Side Request Forgery
CVE-2025-20371 is a high-severity server-side request forgery vulnerability in Splunk Enterprise from Splunk, with a CVSS 3.1 base score of 8.8 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.0.1, 9.4.4, 9.3.6 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.49% 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.0.1 or 9.4.4 or 9.3.6 or 9.2.8, whichever matches your release line, or a later version.
- Update Splunk Cloud Platform to 9.3.2411.109 or 9.3.2408.119 or 9.2.2406.122, whichever matches your release line, or a later version.
- Update Splunk to 9.2.8 or 9.3.6 or 9.4.4, 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.0 up to, but not including, 10.0.1; 9.4 up to, but not including, 9.4.4; 9.3 up to, but not including, 9.3.6; 9.2 up to, but not including, 9.2.8 | 10.0.1, 9.4.4, 9.3.6, 9.2.8 |
| Splunk | Splunk Cloud Platform | 9.3.2411 up to, but not including, 9.3.2411.109; 9.3.2408 up to, but not including, 9.3.2408.119; 9.2.2406 up to, but not including, 9.2.2406.122 | 9.3.2411.109, 9.3.2408.119, 9.2.2406.122 |
| Splunk | Splunk | 9.2.0 up to, but not including, 9.2.8; 9.3.0 up to, but not including, 9.3.6; 9.4.0 up to, but not including, 9.4.4; 10.0.0 | 9.2.8, 9.3.6, 9.4.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
- 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
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (cisco.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
In Splunk Enterprise versions below 10.0.1, 9.4.4, 9.3.6 and 9.2.8, and Splunk Cloud Platform versions below 9.3.2411.109, 9.3.2408.119 and 9.2.2406.122, an unauthenticated attacker could trigger a blind server-side request forgery (SSRF) potentially letting an attacker perform REST API calls on behalf of an authenticated high-privileged user.
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: 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 Server-Side Request Forgery vulnerabilities
- 8.6 High severity
- 8.6 High severity
- 8.6 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.2 High severity
Spotted an error? Tell us.