CVE-2026-20259 Improper Access Control in Splunk Enterprise
A high-privilege user can reassign saved search ownership to unauthorized users due to missing access controls on the ownership endpoint.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-20259?
CVE-2026-20259 is a medium-severity missing authorization vulnerability in Splunk Splunk, published on 10 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
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.
Weakness: CWE-284
Which versions are affected by CVE-2026-20259?
It affects 2 products.
Products include Splunk Splunk, Splunk Splunk Cloud Platform.
How do I fix CVE-2026-20259?
No fix has been published for CVE-2026-20259 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-20259 being exploited?
There is no known exploitation of CVE-2026-20259 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-jhf8-vwfv-vr95.