Splunk Enterprise Security remote code execution via path traversal in REST API
- Exploited
- No known exploitation
- Fix
- Fixed in 8.7.0
- Who is exposed
- Specific setups only
Summary
Splunk Enterprise Security has a flaw that lets a user with the "ess_admin" Splunk Enterprise Security role run arbitrary code on the search head as the account that runs Splunk Enterprise, by combining lookup file upload with Configuration Checker functionality. The attack can be carried out over the network, but the attacker must first log in with that high-privilege role.
Written by a model
Original 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 (help.splunk.com/
Who should check
Teams running Splunk Enterprise Security below 8.7.0 on search heads, including Splunk Enterprise Security users holding the ess_admin role.
“In Splunk Enterprise Security versions below 8.7.0”
What to do
Check whether your setup matches what the bug needs.
Splunk Enterprise Security versions below 8.7.0 The attacker holds the ess_admin Splunk Enterprise Security role The attacker combines lookup file upload with Configuration Checker functionalityUpgrade to a fixed version: 8.7.0.
Workaround: Turn off or remove the Splunk Enterprise Security app.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131202 (Remote Code Execution (RCE) through REST API Path Traversal in Splunk Enterprise Security), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131202 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise Security versions below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- The attacker holds the ess_admin Splunk Enterprise Security role (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- The attacker combines lookup file upload with Configuration Checker functionality (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
Workaround: Turn off or remove the Splunk Enterprise Security app. (source: https://www.cve.org/CVERecord?id=CVE-2026-131202)
CISA KEV: CVE-2026-131202 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131202 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1106
- https://www.cve.org/CVERecord?id=CVE-2026-131202
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131202
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131202"}.Affected versions
- Splunk Splunk Enterprise Securityfixed in 8.7.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- cve.now early warning
Splunk patches nearly 140 flaws across Enterprise, Enterprise Security and SOAR
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1106 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131202 |
| Record | NVD · CVE-2026-131202 |
Questions about CVE-2026-131202
Is CVE-2026-131202 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A user holding the ess_admin role can combine lookup file upload with the Configuration Checker feature and path traversal through the REST API to run arbitrary code on the search head. The code runs as the user account that runs Splunk Enterprise.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131202?
Splunk Enterprise Security: before 8.7.0.
Source: cve.now feed data
Am I affected, and how do I check?
Splunk Enterprise Security versions below 8.7.0 are affected. To check your version, look at the Enterprise Security app version in Splunk Web or its app configuration; the attack requires the ess_admin role and use of lookup file upload with Configuration Checker.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131202?
Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.
Source: advisory.splunk.com, cve.org
Related
- SZB-a6f77657b8Started as this early warning
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.