CVE-2026-76296: Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.4 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.8 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.11 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.16
Event History
Frequently Asked Questions
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.
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.
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.
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.