Skip to content

CVE-2026-131202

Splunk Enterprise Security remote code execution via lookup path traversal for ess_admin users (CVE-2026-131202)

Critical 9.1 Vendor: Cisco Published

CVE-2026-131202: Splunk Enterprise Security before 8.7.0 lets ess_admin users execute code on the search head through lookup upload and Configuration Checker path traversal. Critical CVSS 9.1. Upgrade to 8.7.0.

What happened

An account with the ess_admin role in Splunk Enterprise Security can combine unrestricted lookup file uploads with path handling in the Configuration Checker to execute arbitrary code on the search head. The code runs as the account that runs Splunk Enterprise, not merely within the Security app.

This is a path traversal weakness (CWE-22) and is rated critical with a CVSS 3.1 score of 9.1. The vector is network reachable, has low attack complexity and requires high privileges, needs no user interaction, has changed scope, and has high confidentiality, integrity and availability impact.

The CVE record does not record exploitation or public disclosure. The fixed release is Splunk Enterprise Security 8.7.0.

Who is affected

Splunk Enterprise Security versions before 8.7.0 are affected. Exposure requires an account holding the ess_admin role. Organisations that have granted ess_admin broadly should treat this as relevant even if the role is limited, because the account can execute code as the Splunk Enterprise service account on the search head.

What to do now

  1. Upgrade to Splunk Enterprise Security 8.7.0. Splunk's advisory identifies this as the fixed release.
  2. Review every account holding ess_admin and remove or reduce the role where it is not required. The vulnerability depends on this role, so reducing that group limits exposure while upgrades are planned.
  3. No workaround is listed in the advisory. If the upgrade cannot be applied immediately, restrict access to the search head and monitor for unexpected processes under the Splunk service account and for lookup uploads followed by Configuration Checker activity.

How to detect it

Because code executes as the service account, look for unexpected processes running on search heads under that account. Correlate audit records of lookup file uploads by ess_admin users with subsequent Configuration Checker jobs, and review any lookup paths outside the intended directories.

Beyond the patch

Beyond the patch, this is a reminder that a trusted high-privilege account inside a security tool can be the pivot to full search-head compromise. Spirity's Implementation & Assessment Services can test for path traversal and role-based access control gaps, and Managed Detection & Response (MDR) monitors for the code execution and privilege abuse that follows. Since Splunk is often a core security control, tracking its patch cycle belongs in Supply Chain Defense & Third-Party Risk.

Affected and fixed versions

ProductAffectedFixed in
Splunk Enterprise Security– < 8.7.08.7.0

References

Sources: the CVE record (MITRE), NVD, CISA KEV and SSVC, ENISA EUVD, FIRST EPSS and the vendor's own advisory. Scores and dates are shown as those sources publish them.

Written with AI assistance from the sources above and checked automatically against them before publication.