Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-76296 Overview
CVE-2026-76296 is a missing authorization vulnerability [CWE-862] in Splunk Enterprise. A low-privileged user without the admin or power role can create, move, edit, or delete sourcetype renaming configurations in apps they do not have permission to access. The flaw exists because Splunk Web does not verify app permissions before performing sourcetype renaming operations. Affected versions include Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, and 9.4.16.
Critical Impact
Authenticated low-privilege users can tamper with sourcetype renaming configurations across apps, altering how data is classified at search time and potentially disrupting detections built on sourcetype logic.
Affected Products
- Splunk Enterprise versions below 10.4.4
- Splunk Enterprise versions below 10.2.8
- Splunk Enterprise versions below 10.0.11 and 9.4.16
Discovery Timeline
- 2026-10-21 - CVE-2026-76296 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-76296
Vulnerability Analysis
Splunk uses sourcetype renaming to reassign the sourcetype field of events at search time. These configurations live in app-scoped props.conf files and are referenced by searches, dashboards, and detections. When a user modifies sourcetype renaming in Splunk Web, the server should check whether the user holds the required app permissions before writing the configuration.
In affected versions, Splunk Web skips that check. A user without the admin or power role can create, move, edit, or delete their own sourcetype renaming entries inside apps they are not authorized to access. The vulnerability requires that Splunk Web be enabled and that the attacker holds a valid Splunk account.
The impact is limited to integrity of sourcetype renaming configurations. Confidentiality and availability of events themselves are not directly affected, but downstream searches and detections that rely on sourcetype values can produce incorrect results.
Root Cause
The root cause is a missing authorization check [CWE-862] in the Splunk Web code path that handles sourcetype renaming operations. The handler relies on object ownership but does not validate the user's permissions on the target app before persisting changes.
Attack Vector
The attack vector is network-based through Splunk Web. An authenticated low-privileged user issues requests to create, edit, move, or delete sourcetype renaming configurations within apps they would otherwise not be able to modify. No user interaction and no elevated role is required.
No verified proof-of-concept code is available. See the Splunk Security Advisory SVD-2026-1007 for vendor technical details.
Detection Methods for CVE-2026-76296
Indicators of Compromise
- Unexpected changes to props.conf stanzas containing rename directives inside apps the modifying user should not administer.
- Audit log entries in _audit showing sourcetype renaming configuration writes by users lacking the admin or power role.
- New or deleted sourcetype rename objects attributed to accounts that do not normally manage knowledge objects.
Detection Strategies
- Search the Splunk _audit index for action=edit or action=delete events against props.conf or sourcetype rename objects performed by non-admin users.
- Baseline authorized owners of sourcetype rename knowledge objects and alert on deviations.
- Correlate configuration changes with subsequent anomalies in event classification or detection fidelity.
Monitoring Recommendations
- Forward Splunk internal logs (_internal, _audit) to a centralized monitoring pipeline for review.
- Alert on knowledge object changes to shared or security-related apps performed outside change windows.
- Review Splunk Web access logs for repeated REST calls to /servicesNS/*/*/data/props/sourcetype-rename endpoints by low-privileged accounts.
How to Mitigate CVE-2026-76296
Immediate Actions Required
- Upgrade Splunk Enterprise to version 10.4.4, 10.2.8, 10.0.11, 9.4.16, or later.
- Audit existing sourcetype renaming configurations for unauthorized modifications and revert as needed.
- Review user role assignments and remove unnecessary accounts from systems exposing Splunk Web.
Patch Information
Splunk has released fixed builds in the 10.4.4, 10.2.8, 10.0.11, and 9.4.16 release lines. Refer to the Splunk Security Advisory SVD-2026-1007 for complete remediation details and build identifiers.
Workarounds
- Disable Splunk Web (SPLUNK_WEB=false or web.confstartwebserver = 0) on instances where it is not required, which prevents the vulnerable code path from being reached.
- Restrict network access to Splunk Web to trusted administrative networks only.
- Limit account creation and tighten role assignments so that only trusted users can authenticate to Splunk Web.
# Disable Splunk Web on indexers or forwarders where it is not needed
# $SPLUNK_HOME/etc/system/local/web.conf
[settings]
startwebserver = 0
# Then restart Splunk
$SPLUNK_HOME/bin/splunk restart
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

