CVE-2026-20239 Sensitive Information Disclosure through Log Files in Splunk Enterprise
Users with access to the internal index can view sensitive session cookies and response bodies in log 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-20239?
CVE-2026-20239 is a high-severity vulnerability in Splunk Splunk, published on 20 May 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.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a role that has access to the `_internal` index could view session cookies and response bodies that contain sensitive data.
Weakness: CWE-532
Which versions are affected by CVE-2026-20239?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2026-20239?
No fix has been published for CVE-2026-20239 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-20239 being exploited?
There is no known exploitation of CVE-2026-20239 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-7mj7-jqh4-hc7f.