CVE-2026-20239
Sensitive Information Disclosure through Log Files in Splunk Enterprise
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.2.2, 10.0.5, 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.2 · fixed in 10.2.2; From 10.0 · fixed in 10.0.5
- Splunk Splunk Cloud Platform
From 10.3.2512 · fixed in 10.3.2512.8; From 10.2.2510 · fixed in 10.2.2510.11; From 10.1.2507 · fixed in 10.1.2507.21; From 10.0.2503 · fixed in 10.0.2503.13