CVE-2026-20259: Improper Access Control in Splunk Enterprise

Published Jun 10, 2026
·
Updated

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 editsavedsearchowner could reassign saved search ownership to users outside their authorized scope. The ownership reassignment endpoint lacks access control.

Affected Software

9 affected components
Splunk Splunk Enterprise<10.2.4, <10.0.7
Splunk Splunk Cloud Platform<10.4.2604.0, <10.3.2512.12, <10.2.2510.15, <10.1.2507.23, <10.0.2503.14, <9.3.2411.131
Splunk splunk>=10.0.0<10.0.7
Splunk splunk>=10.2.0<10.2.4
Splunk Splunk Cloud Platform>=9.3.2411<9.3.2411.131
Splunk Splunk Cloud Platform>=10.0.2503<10.0.2503.14
Splunk Splunk Cloud Platform>=10.1.2507<10.1.2507.23
Splunk Splunk Cloud Platform>=10.2.2510<10.2.2510.15
Splunk Splunk Cloud Platform>=10.3.2512<10.3.2512.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.4
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.7
  3. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.4.2604.0
  4. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.3.2512.12
  5. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.2.2510.15
  6. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.1.2507.23
  7. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.0.2503.14
  8. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 9.3.2411.131

Event History

Jun 10, 2026
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-20259?

The severity of CVE-2026-20259 is rated as medium with a score of 5.5.

2

What software is affected by CVE-2026-20259?

CVE-2026-20259 affects Splunk Enterprise versions below 10.2.4 and 10.0.7, as well as 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.

3

How do I fix CVE-2026-20259?

To fix CVE-2026-20259, upgrade Splunk Enterprise to version 10.2.4 or above, or Splunk Cloud Platform to version 10.4.2604.0 or above.

4

What is the risk associated with CVE-2026-20259?

CVE-2026-20259 presents a risk score of 39, indicating potential unauthorized access under certain conditions.

5

What capabilities allow exploitation of CVE-2026-20259?

The vulnerability can be exploited by users holding a Splunk role with the `edit_saved_search_owner` high-privilege capability.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203