CVE-2026-20138: Sensitive Information Disclosure in "_internal" index in Splunk Enterprise
In Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.9, and 9.2.11, a user of a Splunk Search Head Cluster (SHC) deployment who holds a role with access to the Splunk internal index could view the integrationKey, secretKey, and appSecretKey secrets, generated by Duo Two-Factor Authentication for Splunk Enterprise, in plain text.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-20138?
CVE-2026-20138 has been classified as a high severity vulnerability.
How do I fix CVE-2026-20138?
To fix CVE-2026-20138, upgrade your Splunk Enterprise to version 10.2.0 or later.
What versions of Splunk Enterprise are affected by CVE-2026-20138?
CVE-2026-20138 affects Splunk Enterprise versions below 10.2.0, 10.0.2, 9.4.7, 9.3.9, and 9.2.11.
What are the risks associated with CVE-2026-20138?
The risks associated with CVE-2026-20138 include unauthorized exposure of sensitive secrets such as integrationKey, secretKey, and appSecretKey.
Who is impacted by CVE-2026-20138?
Users of a Splunk Search Head Cluster deployment with specific access roles are impacted by CVE-2026-20138.