CVE-2026-20141
Improper Access Control in Splunk Monitoring Console Causes Data Disclosure
Publication date: 2026-02-18
Last updated on: 2026-02-23
Assigner: Cisco Systems, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| splunk | splunk | From 10.0.0 (inc) to 10.0.3 (exc) |
| splunk | splunk | From 9.3.0 (inc) to 9.3.9 (exc) |
| splunk | splunk | From 9.4.0 (inc) to 9.4.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-20141 is an improper access control vulnerability in the Splunk Monitoring Console App affecting certain versions of Splunk Enterprise.'}, {'type': 'paragraph', 'content': 'Specifically, low-privileged users who do not have the "admin" role can access Monitoring Console endpoints that should be restricted.'}, {'type': 'paragraph', 'content': 'This unauthorized access can lead to the disclosure of sensitive information.'}, {'type': 'paragraph', 'content': 'The vulnerability affects Splunk Enterprise versions prior to 10.0.2, 10.0.3, 9.4.8, and 9.3.9, but does not affect the Cloud Monitoring Console or Splunk Cloud Platform instances.'}] [1]
How can this vulnerability impact me? :
This vulnerability allows low-privileged users to access sensitive information through the Monitoring Console endpoints without proper authorization.
While it does not impact confidentiality directly according to the CVSS score, it has a low integrity impact, meaning unauthorized users could potentially view or influence some data they should not access.
There is no impact on availability.
Overall, this could lead to sensitive information disclosure within your Splunk Enterprise environment if the vulnerable versions are used.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
No detection methods or specific commands to identify this vulnerability on your network or system are provided.
What immediate steps should I take to mitigate this vulnerability?
The only recommended mitigation is to upgrade Splunk Enterprise to the fixed versions: 10.0.3, 9.4.8, or 9.3.9, depending on your current version.
No other mitigations or workarounds are available.