CVE-2026-76317: Path Traversal through the Lookup Configuration REST API in Splunk Enterprise
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could move files that the user account running Splunk Enterprise can read into a lookup that the user controls. The user could then access all relevant data and affect system integrity and availability on the search head. The vulnerability is possible because the lookup configuration endpoint does not resolve lookup source paths before checking whether they stay inside the allowed lookup staging area. For more information see About lookups (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/use-lookups-in-splunk-web/about-lookups) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) 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.2 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.14
Event History
Frequently Asked Questions
Which users can exploit this issue?
A user who does not have the Splunk "admin" or "power" roles can exploit it, provided they can control a lookup. The issue affects the lookup configuration REST API.
What access does an attacker need?
The attacker needs an existing Splunk user account with permissions sufficient to control a lookup. Exploitation does not require user interaction and can be performed remotely through the REST API.
What systems or files are at risk?
Files readable by the operating-system account running Splunk Enterprise may be moved into an attacker-controlled lookup and accessed there. The issue can also affect integrity and availability on the search head.
Which versions should be remediated?
Upgrade to 10.4.2, 10.2.6, 10.0.9, or 9.4.14, as applicable. Versions below those releases are affected.