CVE-2026-20259
Improper Access Control 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.4, 10.0.7, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, and 2 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: partial
Summary
In Splunk Enterprise versions below 10.2.4 and 10.0.7, and Splunk Cloud Platform versions below 10.4.2604.0, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, 10.0.2503.14, and 9.3.2411.131, a user who holds a Splunk role that contains the high-privilege capability `edit_saved_search_owner` could reassign saved search ownership to users outside their authorized scope. The ownership reassignment endpoint lacks access control.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Splunk Splunk Enterprise
From 10.2 · fixed in 10.2.4; From 10.0 · fixed in 10.0.7
- Splunk Splunk Cloud Platform
From 10.3.2512 · fixed in 10.3.2512.12; From 10.2.2510 · fixed in 10.2.2510.15; From 10.1.2507 · fixed in 10.1.2507.23; From 10.0.2503 · fixed in 10.0.2503.14; From 9.3.2411 · fixed in 9.3.2411.131