CVE-2025-20389
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored client-side denial of service vulnerability exists in Splunk Secure Gateway app where low-privileged users can inject malicious JavaScript/HTML through the 'label' column field when adding a new device. This payload executes in other users' browsers when viewing the device, causing client-side DoS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.2.0, < 9.2.10>= 9.3.0, < 9.3.8>= 9.4.0, < 9.4.6>= 10.0.0, < 10.0.2>= 9.3.2411, < 9.3.2411.120>= 10.0.2503, < 10.0.2503.8>= 10.1.2507, < 10.1.2507.6>= 3.7.0, < 3.7.28>= 3.8.0, < 3.8.58>= 3.9.0, < 3.9.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Splunk Enterprise versionNavigate to Settings > About > Version or run the 'splunk version' command from the Splunk bin directoryAffected if installed version falls within any of these ranges: 9.2.0 to 9.2.9, 9.3.0 to 9.3.7, 9.4.0 to 9.4.5, or 10.0.0 to 10.0.1
-
Identify Splunk Secure Gateway app versionNavigate to Apps > Manage Apps, locate the 'Splunk Secure Gateway' app, and note the version number displayedAffected if app version is 3.7.0 to 3.7.27, 3.8.0 to 3.8.57, or 3.9.0 to 3.9.9
-
Check if Splunk Secure Gateway is installed and enabledIn Splunk Web, go to Apps > Manage Apps and verify the Splunk Secure Gateway app status shows as 'Enabled'Affected if the app is installed and enabled in the Splunk environment
-
Verify device management feature accessCheck Splunk Secure Gateway app settings for device or endpoint management configuration accessible to standard or low-privileged usersAffected if non-admin users have access to add or manage devices through the app
-
Inspect label field in device creationWhen adding a new device in Splunk Secure Gateway, examine the 'label' field input in the device creation formAffected if the label field accepts freeform text input without visible sanitization or validation indicators
The environment is affected if Splunk Enterprise or Splunk Secure Gateway app version falls within the affected ranges AND the Splunk Secure Gateway app is enabled with device management accessible to low-privileged users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.7.283.8.583.9.10
Upgrade Splunk Enterprise to version 10.0.2, 9.4.6, 9.3.8, or 9.2.10 (or Splunk Secure Gateway app to 3.9.10, 3.8.58, or 3.7.28 on Splunk Cloud Platform), and implement input validation/sanitization on the 'label' field.
Splunk Enterprise: 10.0.2, 9.4.6, 9.3.8, or 9.2.10 | Splunk Secure Gateway: 3.9.10, 3.8.58, or 3.7.28
- 1. Identify the currently installed Splunk Enterprise version by navigating to Settings > About > Version information.
- 2. Identify the currently installed Splunk Secure Gateway app version by navigating to Apps > Manage Apps.
- 3. For Splunk Enterprise: upgrade to version 10.0.2, 9.4.6, 9.3.8, or 9.2.10 (or later) following the standard upgrade process at docs.splunk.com/Documentation/Splunk/latest/Installation/HowtoupgradeSplunk.
- 4. For Splunk Cloud Platform: the cloud platform upgrades are managed by Splunk; contact Splunk Support to request the patched version.
- 5. For Splunk Secure Gateway app: navigate to Apps > Manage Apps and update the Splunk Secure Gateway app to version 3.9.10, 3.8.58, or 3.7.28 (or later) from Splunkbase.
- 6. After upgrading, verify the fix by confirming the version numbers in Settings > About > Version information and Apps > Manage Apps.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20389 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20389 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data