CVE-2026-20164 Sensitive Information Disclosure through Improper Access Control in Splunk Enterprise
Low-privileged users can access a REST API endpoint to view sensitive password hashes or plaintext values from configuration files.
- 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-20164?
CVE-2026-20164 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.0, 10.0.3, 9.4.9, and 9.3.10, and Splunk Cloud Platform versions below 10.2.2510.5, 10.1.2507.16, 10.0.2503.11, and 9.3.2411.123, a low-privileged user that does not hold the "admin" or "power" Splunk roles could access the `/splunkd/__raw/servicesNS/-/-/configs/conf-passwords` REST API endpoint, which exposes the hashed or plaintext password values that are stored in the passwords.conf configuration file due to improper access control. This vulnerability could allow for the unauthorized disclosure of sensitive credentials.
Weakness: CWE-200
Which versions are affected by CVE-2026-20164?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2026-20164?
No fix has been published for CVE-2026-20164 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-20164 being exploited?
There is no known exploitation of CVE-2026-20164 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-fc3g-2crx-rgcj.