dbcve.org
SplunkApplication

CVE-2026-20165

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 9.3.10 / 9.3.2411.124 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
In Splunk Enterprise versions below 10.2.1, 10.0.4, 9.4.9, and 9.3.10, and Splunk Cloud Platform versions below 10.2.2510.7, 10.1.2507.17, 10.0.2503.12, and 9.3.2411.124, a low-privileged user that does not hold the "admin" or "power" Splunk roles could retrieve sensitive information by inspecting the job's search log due to improper access control in the MongoClient logging channel.

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 confidence

A low-privileged Splunk user without admin or power roles can retrieve sensitive information by inspecting job search logs due to improper access control in the MongoClient logging channel, enabling unauthorized disclosure of data that should be restricted based on role permissions.

MitigationUpgrade Splunk Enterprise to versions 10.2.1, 10.0.4, 9.4.9, or 9.3.10 (or Splunk Cloud Platform to 10.2.2510.7, 10.1.2507.17, 10.0.2503.12, or 9.3.2411.124) to patch the improper access control vulnerability in the MongoClient logging channel.

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
SplunkApplication
Affected:>= 9.3.0, < 9.3.10>= 9.4.0, < 9.4.9>= 10.0.0, < 10.0.4= 10.2.0
Splunk Cloud PlatformApplication
Affected:>= 9.3.2411, < 9.3.2411.124>= 10.0.2503, < 10.0.2503.12>= 10.1.2507, < 10.1.2507.17>= 10.2.2510, < 10.2.2510.7

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Splunk Enterprise version
    Run: splunk --version or access $SPLUNK_HOME/etc/splunk.version to read the version file
    Affected if Version falls within >= 9.3.0, < 9.3.10 OR >= 9.4.0, < 9.4.9 OR >= 10.0.0, < 10.0.4 OR equals 10.2.0
  2. Check installed Splunk Cloud Platform version
    Navigate to Settings > About > Version information in the Splunk Cloud console or check via splunkcloud.com/home/
    Affected if Version falls within >= 9.3.2411, < 9.3.2411.124 OR >= 10.0.2503, < 10.0.2503.12 OR >= 10.1.2507, < 10.1.2507.17 OR >= 10.2.2510, < 10.2.2510.7
  3. Verify if non-admin users have access to job search logs
    Log in as a user without admin or power roles and attempt to access the job inspector or search log history via the Jobs endpoint or by visiting the Activity > Jobs page
    Affected if A low-privileged user can view search job details or logs that should be restricted based on role permissions
  4. Review MongoClient logging visibility
    Inspect whether job search results or debug output contains MongoClient connection strings, database queries, or internal logging data not intended for the user's role
    Affected if Users can see MongoClient or internal database logging output in their search job results that should be restricted

If your Splunk version falls within any of the affected ranges AND low-privileged users can access job search logs or internal logging data, your environment is likely affected by this improper access control vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.3.10 / 9.3.2411.124 / 9.4.9 or later
Fixed in 9.3.109.3.2411.1249.4.9
Interim mitigation

Upgrade Splunk Enterprise to versions 10.2.1, 10.0.4, 9.4.9, or 9.3.10 (or Splunk Cloud Platform to 10.2.2510.7, 10.1.2507.17, 10.0.2503.12, or 9.3.2411.124) to patch the improper access control vulnerability in the MongoClient logging channel.

Recommended fix High confidence

Upgrade to Splunk Enterprise 9.3.10+, 9.4.9+, 10.0.4+, or 10.2.1+ (or the equivalent Splunk Cloud Platform patch level for your version)

  1. Identify the currently installed Splunk Enterprise or Splunk Cloud Platform version using the 'splunk version' command or the Cloud Console
  2. For Splunk Enterprise 9.3.x: Upgrade to version 9.3.10 or later
  3. For Splunk Enterprise 9.4.x: Upgrade to version 9.4.9 or later
  4. For Splunk Enterprise 10.0.x: Upgrade to version 10.0.4 or later
  5. For Splunk Enterprise 10.2.x: Upgrade to version 10.2.1 or later
  6. For Splunk Cloud Platform 9.3.x: Upgrade to version 9.3.2411.124 or later
  7. For Splunk Cloud Platform 10.0.x: Upgrade to version 10.0.2503.12 or later
  8. For Splunk Cloud Platform 10.1.x: Upgrade to version 10.1.2507.17 or later
Caveat Review Splunk release notes for any breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20165 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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