CVE-2025-20389: Splunk Enterprise · The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Splunk Splunk Enterprise | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-20389, European organizations should promptly upgrade affected Splunk Enterprise versions to 10.0.2, 9.4.6, 9.3.8, or 9.2.10 or later, and update the Splunk Secure Gateway app to versions 3.9.10, 3.8.58, or 3.7.28 or later. Until patches are applied, restrict low-privileged user capabilities to add devices or manipulate the 'label' field within the Secure Gateway app. Implement strict input validation and sanitization controls on client-side inputs, especially for fields that influence control or data flow. Monitor Splunk logs for unusual activity related to device additions or malformed inputs. Employ network segmentation and access controls to limit exposure of Splunk management interfaces to trusted users only. Conduct regular audits of user roles and permissions to minimize the number of accounts with device addition privileges. Additionally, consider deploying client-side protections such as browser security policies or endpoint monitoring to detect and prevent client-side DoS conditions. Finally, maintain an incident response plan that includes procedures for handling Splunk service disruptions.
Description
In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and versions below 3.9.10, 3.8.58 and 3.7.28 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the `label` column field after adding a new device in the Splunk Secure Gateway app. This could potentially lead to a client-side denial of service (DoS).