CVE-2026-20165 Sensitive Information Disclosure in MongoClient logging channel in Splunk Enterprise
Low-privileged users can retrieve sensitive information from search logs due to improper access control in the MongoClient logging channel.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-20165?
CVE-2026-20165 is a medium-severity vulnerability in Splunk Splunk, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-532
Which versions are affected by CVE-2026-20165?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2026-20165?
No fix has been published for CVE-2026-20165 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-20165 being exploited?
There is no known exploitation of CVE-2026-20165 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-m4gj-655q-gvm8.