Skip to content
VulniPulse
Critical9.1Splunk Updated

CVE-2026-131202: Remote Code Execution (RCE) through REST API Path Traversal in Splunk Enterprise Security

This Splunk advisory covers CVE-2026-131202 in Splunk Enterprise Security.

Open the Splunk advisory

Key facts

Vendor rating
Critical, CVSS 9.1
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H · base score 9.1, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: high. User interaction: none. Scope: changed. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-22 The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Splunk Enterprise Security before 8.7.0
Fixed in
8.7.0
Source published
Source revised
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

SplunkSplunk EnterpriseES / ITSI / SOAR

Description

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the search head as the user account running Splunk Enterprise by combining lookup file upload and Configuration Checker functionality.

The vulnerability is possible because Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory. For more information see Users and roles for Splunk Enterprise Security ( ) and Create and manage lookups in Splunk Enterprise Security ( ) in the Splunk documentation.

Text from the source record.

Affected versions
  • Splunk Enterprise Security before 8.7.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-131202

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation.

Workarounds

  • The vulnerability is possible because Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory.

End-of-life dates for Splunk Enterprise

Splunk advisories, November 2026All Splunk advisories

Get an email when Splunk Enterprise publishes the next one.

See Splunk Enterprise's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Splunk Enterprise