Act nowDisclosed

Advisory · CVE-2026-131202

Authenticated RCE in Splunk Enterprise Security via lookup upload path traversal

A user with the ess_admin role can combine lookup file upload with Configuration Checker functionality to execute arbitrary code on the search head as the Splunk Enterprise service account.

Vendor
Splunk
Product
Splunk Enterprise Security
Identifier / CWE
CVE-2026-131202
CWE-22
Action timing
Immediate
ELI5

Explain it like I’m five

A security admin uploads a lookup file, but the app does not check where the file really goes. By pointing the upload outside its intended folder, the admin's account can plant code that Splunk then runs as itself.

SIMPLIFIED_ATTACK_PATH04 STEPS
  1. 01Privileged access

    An attacker holds a user account with the ess_admin Splunk Enterprise Security role.

  2. 02Lookup upload

    The attacker uploads a lookup file through the app, and Splunk does not restrict the file type.

  3. 03Path escapes

    Configuration Checker module paths are not kept inside the intended directory, so the uploaded file lands where the attacker chooses.

  4. 04Code runs as Splunk

    The planted file is executed on the search head as the user account running Splunk Enterprise.

What happened

Splunk disclosed CVE-2026-131202 in advisory SVD-2026-1106 on November 19, 2026. Splunk Enterprise Security versions below 8.7.0 are affected, and the fix is version 8.7.0. The vulnerability scores 9.1 CVSS (CWE-22, path traversal).

A user who holds the ess_admin role can execute arbitrary code on the search head as the user account running Splunk Enterprise by combining lookup file upload and Configuration Checker functionality. Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory.

What to do

  1. Upgrade Splunk Enterprise Security (and Splunk App for PCI Compliance, if installed) to version 8.7.0 or higher.
  2. Until patched, consider turning off or removing the Splunk Enterprise Security app where it is not required, per Splunk’s stated workaround.
  3. Review who holds the ess_admin role and remove it from accounts that do not need it.
  4. Audit lookup uploads and Configuration Checker activity for unexpected files or module paths outside the intended directories.
  5. Check the search head for unexpected processes or files running as the Splunk service account.

Management note

This is a privileged-user path to full code execution on the search head of a security platform, the system that holds the organisation’s detection data and credentials. It needs an ess_admin account, so it is a strong argument for tight role assignment and for patching the SIEM itself with the same urgency as the systems it watches.