CVE-2026-20141
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, 10.0.3, 9.4.8, and 9.3.9, a low-privileged user who does not hold the "admin" Splunk role could access the Splunk Monitoring Console App endpoints due to an improper access control. This could lead to a sensitive information disclosure.<br><br>The Monitoring Console app is a bundled app that comes with Splunk Enterprise. It is not available for download on SplunkBase, and is not installed on Splunk Cloud Platform instances. This vulnerability does not affect [Cloud Monitoring Console](https://help.splunk.com/en/splunk-cloud-platform/administer/admin-manual/10.2.2510/monitor-your-splunk-cloud-platform-deployment/introduction-to-the-cloud-monitoring-console).
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 confidenceSplunk Enterprise contains an improper access control vulnerability in the Monitoring Console bundled app. Low-privileged users who do not hold the admin role can access Monitoring Console endpoints that should be restricted to administrators, potentially exposing sensitive deployment information.
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.3.0, < 9.3.9>= 9.4.0, < 9.4.8>= 10.0.0, < 10.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Splunk Enterprise versionRun `splunk version` from the Splunk bin directory or access About > Version in the Splunk web interfaceAffected if The installed version falls within 9.3.0-9.3.8, 9.4.0-9.4.7, or 10.0.0-10.0.2 (i.e., less than 9.3.9, 9.4.8, or 10.0.3)
-
Verify Monitoring Console app is presentNavigate to Apps > Manage Apps in Splunk web interface and confirm the 'Splunk Monitoring Console' app is installed and enabledAffected if The Monitoring Console app is installed and enabled on a vulnerable Splunk version
-
Identify users with non-admin rolesAccess Settings > Users and roles to review all defined roles. Identify users assigned to roles other than 'admin' or 'splunk-system-role'Affected if There are users assigned to low-privileged roles (e.g., user, power, analyst) who should not have administrative access
-
Confirm Monitoring Console endpoint accessibilityAttempt to access Monitoring Console URLs (e.g., /en-US/app/splunk_monitoring_console) using a low-privileged user account that does not hold the admin roleAffected if A low-privileged user can successfully access Monitoring Console endpoints that should be restricted to administrators
A user is affected if they run a vulnerable Splunk Enterprise version (below 9.3.9, 9.4.8, or 10.0.3) AND have non-admin users who can access the Monitoring Console bundled app.
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.3.99.4.810.0.3
Upgrade Splunk Enterprise to version 10.0.2, 10.0.3, 9.4.8, 9.3.9 or later to remediate this vulnerability.
Upgrade to Splunk Enterprise 9.3.9, 9.4.8, or 10.0.3 (depending on your current major version line)
- Identify your current Splunk Enterprise version by navigating to Settings > About > Version information in the Splunk web interface
- Backup your Splunk configuration and data directories before performing the upgrade
- Download the appropriate fixed version from splunk.com: For 9.3.x line, upgrade to 9.3.9; For 9.4.x line, upgrade to 9.4.8; For 10.0.x line, upgrade to 10.0.3
- Stop the Splunk Enterprise service using: $SPLUNK_HOME/bin/splunk stop
- Install the upgrade following standard Splunk upgrade procedures (for Splunk Enterprise, run the installer or use the tar/zip archive method)
- Start the Splunk Enterprise service using: $SPLUNK_HOME/bin/splunk start
- Verify the upgrade was successful by checking the version in Settings > About > Version information
- Confirm the vulnerability is remediated by verifying that non-admin users can no longer access Monitoring Console endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20141 — 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-2026-20141 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