CVE-2026-76296: Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise

Published Oct 21, 2026
·
Updated

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could create, move, edit, or delete sourcetype renaming configurations that they own in apps that they do not have permission to access. The vulnerability is possible when Splunk Web is turned on because Splunk Web does not verify the required app permissions before it performs sourcetype renaming operations. For more information see Rename source types at search time (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.6/configure-source-types/rename-source-types-at-search-time) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.4.4, <10.2.8, <10.0.11, <9.4.16

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.4.4
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.8
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.11
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.16

Event History

Oct 21, 2026
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A user who does not have the Splunk "admin" or "power" role can exploit it, provided they own the sourcetype renaming configuration involved. The issue allows that user to operate on their owned renaming configurations in apps they are not permitted to access.

2

What conditions are required for exploitation?

Splunk Web must be enabled. The affected behavior occurs because Splunk Web does not verify required app permissions before carrying out sourcetype renaming operations.

3

Which operations can an affected user perform?

An affected user can create, move, edit, or delete sourcetype renaming configurations that they own in apps they otherwise lack permission to access.

4

Which Splunk Enterprise versions are affected?

The issue affects Splunk Enterprise versions earlier than 10.4.4, 10.2.8, 10.0.11, and 9.4.16.

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