CVE-2025-20324
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 9.4.2, 9.3.5, 9.2.7, and 9.1.10 and Splunk Cloud Platform versions below 9.3.2411.104, 9.3.2408.113, and 9.2.2406.119, a low-privileged user that does not hold the "admin" or "power" Splunk roles could create or overwrite [system source type](https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/9.2/configure-source-types/create-source-types) configurations by sending a specially-crafted payload to the `/servicesNS/nobody/search/admin/sourcetypes/` REST endpoint on the Splunk management port.
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 confidenceThis is an authorization bypass vulnerability in Splunk Enterprise and Cloud Platform where low-privileged users (non-admin, non-power roles) can create or overwrite system source type configurations by sending specially-crafted payloads to the `/servicesNS/nobody/search/admin/sourcetypes/` REST endpoint on the Splunk management port. Source types define how incoming data is parsed and categorized, making this a configuration integrity issue.
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.1.0, < 9.1.10>= 9.2.0, < 9.2.7>= 9.3.0, < 9.3.5>= 9.4.0, < 9.4.2>= 9.2.2406, < 9.2.2406.119>= 9.3.2408, < 9.3.2408.113>= 9.3.2411, < 9.3.2411.104CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
-
Check installed Splunk Enterprise versionRun `splunk version` from the Splunk binary directory, or inspect $SPLUNK_HOME/etc/splunk.version for the version fieldAffected if Version is >= 9.1.0 and < 9.1.10, OR >= 9.2.0 and < 9.2.7, OR >= 9.3.0 and < 9.3.5, OR >= 9.4.0 and < 9.4.2
-
Check installed Splunk Cloud Platform versionAccess Splunk Cloud management console or use cloud API to retrieve the platform version numberAffected if Version is >= 9.2.2406 and < 9.2.2406.119, OR >= 9.3.2408 and < 9.3.2408.113, OR >= 9.3.2411 and < 9.3.2411.104
-
Identify low-privileged users with REST API accessQuery the /services/authentication/users endpoint or review user role assignments in Splunk management console under Settings > Users and AuthenticationAffected if Any user with a role other than admin or power user has API access capabilities
-
Verify source type endpoint accessibilityUsing a low-privilege user account, attempt a GET request to /servicesNS/nobody/search/admin/sourcetypes/ on the Splunk management port (default 8089)Affected if The request returns a valid response with source type data instead of an authorization error
Your environment is affected if Splunk version falls within any of the affected ranges AND low-privileged users have access to the management REST API endpoint for source types.
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 · scoped9.1.109.2.79.2.2406.119
Upgrade Splunk Enterprise to versions 9.4.2, 9.3.5, 9.2.7, or 9.1.10 (or higher) and Splunk Cloud Platform to versions 9.3.2411.104, 9.3.2408.113, or 9.2.2406.119 (or higher) to patch this vulnerability.
Splunk Enterprise: 9.1.10, 9.2.7, 9.3.5, or 9.4.2 | Splunk Cloud Platform: 9.2.2406.119, 9.3.2408.113, or 9.3.2411.104
- Identify the currently installed Splunk Enterprise or Splunk Cloud Platform version using the Splunk UI (Settings > About) or by running 'splunk version' from the command line
- For Splunk Enterprise: Upgrade to version 9.1.10 (if on 9.1.x), 9.2.7 (if on 9.2.x), 9.3.5 (if on 9.3.x), or 9.4.2 (latest stable release)
- For Splunk Cloud Platform: Contact Splunk Support to request upgrade to version 9.2.2406.119, 9.3.2408.113, or 9.3.2411.104 (depending on your current release track)
- After upgrade, verify the fix by confirming that low-privileged users without admin or power roles can no longer access the /servicesNS/nobody/search/admin/sourcetypes/ endpoint to create or overwrite system source type configurations
- Review Splunk role permissions to ensure users are assigned appropriate roles based on the principle of least privilege
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20324 — 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-20324 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