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-76294 Overview
CVE-2026-76294 is a missing authorization vulnerability in Splunk Enterprise that allows a low-privileged authenticated user to move field extractions or field transformations into apps for which the user lacks read access. The flaw affects Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16. The Representational State Transfer (REST) API does not validate destination app access before processing move operations for field extraction and field transformation knowledge objects. The weakness is tracked under CWE-862 (Missing Authorization) and documented in Splunk Security Advisory SVD-2026-1007.
Critical Impact
An authenticated user without the admin or power Splunk role can place knowledge objects into apps they should not access, affecting the integrity of knowledge object configurations.
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-76294 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-76294
Vulnerability Analysis
Splunk Enterprise exposes REST API endpoints for managing knowledge objects, including field extractions and field transformations. These objects can be moved between Splunk apps using the REST interface. The affected endpoints process move operations without checking whether the authenticated user has read access to the destination app. As a result, a user who is not an admin or power role holder can relocate knowledge objects into apps that should remain outside their visibility and control.
The behavior allows integrity-affecting modifications to knowledge object layouts across app boundaries. While the vulnerability does not expose data from the destination app directly, it enables a non-privileged user to influence configuration state in apps outside their authorized scope.
Root Cause
The root cause is a missing authorization check [CWE-862] in the REST API handler for field extraction and field transformation move operations. The destination app parameter is accepted and acted upon without verifying that the requesting user holds read permission on that app. Splunk's role-based access model relies on the API tier to enforce app-scoped permissions, and this enforcement step is absent on the specific move path.
Attack Vector
Exploitation requires network access to the Splunk REST API and valid credentials for a low-privileged Splunk account that does not hold the admin or power roles. The attacker issues an authenticated REST request to move a field extraction or field transformation object, supplying a destination app for which the account has no read access. The server processes the request without rejecting the operation, completing the unauthorized relocation.
The vulnerability requires no user interaction and no elevated privileges beyond a standard authenticated session. See the Splunk field extractions documentation and knowledge object permissions documentation for the affected operations.
Detection Methods for CVE-2026-76294
Indicators of Compromise
- Audit log entries showing REST API calls to field extraction or field transformation endpoints originating from accounts without admin or power roles.
- Unexpected appearance of field extraction or field transformation objects in apps where the originating user has no read permission.
- splunkd_access.log entries recording successful POST operations against /services/data/props/extractions/ or /services/data/transforms/extractions/ with cross-app destination parameters.
Detection Strategies
- Review Splunk audit logs for move operations performed by non-privileged users against apps they do not own.
- Compare the historical ownership of knowledge objects against current app assignments to identify unauthorized relocations.
- Alert on REST API usage patterns where a single low-privileged account issues multiple app-move requests in a short interval.
Monitoring Recommendations
- Enable detailed REST API audit logging and forward it to a central log store for correlation.
- Baseline the normal set of users who manage field extractions and alert when accounts outside that set invoke the relevant endpoints.
- Monitor knowledge object changes using Splunk's _audit index and flag operations where the acting user's role set does not include admin or power.
How to Mitigate CVE-2026-76294
Immediate Actions Required
- Upgrade Splunk Enterprise to version 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later as applicable to your deployment branch.
- Review existing user role assignments and remove unnecessary access to the REST API for accounts that do not require it.
- Audit field extraction and field transformation objects for recent unauthorized app assignments and restore correct ownership.
Patch Information
Splunk has released fixed versions documented in Splunk Security Advisory SVD-2026-1007. Administrators should apply the patched release that corresponds to their maintenance branch: 10.4.4, 10.2.8, 10.0.11, or 9.4.16. The patch adds the missing destination-app access validation to the REST API handlers for field extraction and field transformation move operations.
Workarounds
- Restrict REST API access at the network layer so that only trusted management hosts can reach Splunk management ports.
- Limit the assignment of custom roles that grant knowledge object edit capabilities to users who require them.
- Enforce multi-factor authentication for all Splunk accounts to reduce the risk of credential misuse against the vulnerable endpoints.
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

