A critical flaw (CVSS 9.1) in Splunk Enterprise Security versions below 8.7.0 lets a user with the "ess_admin" role run arbitrary code on the search head by combining lookup file upload with Configuration Checker functionality.
What Is It
CVE-2026-131202 is a path traversal weakness (CWE-22) in Splunk Enterprise Security. NVD's description says the problem exists for two reasons. First, the product does not restrict which file types can be uploaded as lookups. Second, it does not keep Configuration Checker module paths inside the intended directory. A user holding the "ess_admin" role can chain the two to execute arbitrary code on the search head. That code runs as the user account running Splunk Enterprise. The affected module is listed as the REST API.
Cisco's PSIRT submitted the record. NVD published it on 2026-11-19, and its status is still "Received."
Why It Matters
The CVSS v3.1 vector is AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. The attack works over the network, has low complexity and needs no user interaction. The scope is changed, and confidentiality, integrity and availability impacts are all high. The main limit is that the attacker needs high privileges, specifically the ess_admin role.
A search head in a security operations environment usually has broad access to collected log data. Code execution there therefore matters beyond the application itself.
Exploitation status: No CISA KEV entry was supplied for this CVE, so KEV does not confirm active exploitation. CISA's SSVC assessment, as Coordinator, lists exploitation as "none," automatable as "no" and technical impact as "total."
What's Vulnerable
- Vendor: Splunk
- Product: Splunk Enterprise Security
- Module: REST API
- Affected versions: all versions below 8.7.0
The record lists no specific CPEs.
Patch Status
The record marks versions below 8.7.0 as affected, so version 8.7.0 and later are outside the affected range. Splunk's advisory SVD-2026-1106 is the vendor reference for remediation details. There is no KEV entry, so CISA has set no required action or due date.
Splunk also points to its documentation on Enterprise Security users and roles and on lookup management. Defenders can use those pages to review who holds the ess_admin role.