Splunk Enterprise Security arbitrary SPL command execution in CIM workflow actions
Only affects Splunk Enterprise Security below 8.7.0 on instances with Splunk Web turned on, when a user selects a View Adaptive Response workflow action on an attacker-supplied event. Fixed in 8.7.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.7.0
- Who is exposed
- Specific setups only
Summary
Written by a model
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user who can influence indexed event data could store attacker-controlled values in event fields. If another authenticated user who reviews the event selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action from Event Actions, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the action. The unauthenticated user could then access or modify sensitive data and disrupt services available to the user who selects the action. The vulnerability is possible because the affected Common Information Model workflow actions insert the orig_sid and orig_rid event-field values directly into searches without safely validating or quoting the values. For more information see About workflow actions in Splunk Web (help.splunk.com/
Who should check
Teams running Splunk Enterprise Security below 8.7.0 with Splunk Web turned on, including analysts who review events and use Event Actions workflow actions
“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 Splunk Web turned on A victim user selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action from Event Actions on an event containing the attacker's valuesUpgrade to a fixed version: 8.7.0.
Workaround: Turn off Splunk Web
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-131236 (SPL Injection through Splunk Web Workflow Actions 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-131236 (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)
- Splunk Web turned on (source: https://www.cve.org/CVERecord?id=CVE-2026-131236)
- A victim user selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action from Event Actions on an event containing the attacker's values (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, no login, a user action.
Workaround: Turn off Splunk Web (source: https://www.cve.org/CVERecord?id=CVE-2026-131236)
CISA KEV: CVE-2026-131236 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131236 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-131236
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-131236
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-131236"}.Affected versions
- Splunk Splunk Enterprise Securityfixed in 8.7.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
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-131236 |
| Record | NVD · CVE-2026-131236 |
Questions about CVE-2026-131236
Is CVE-2026-131236 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?
An attacker can plant SPL search commands in event values. When another authenticated user who reviews that event selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action, those commands run with that user's permissions, which can expose or change sensitive data and disrupt services.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131236?
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, but only on instances with Splunk Web turned on. Check the installed version of Splunk Enterprise Security in the app list, and check whether Splunk Web is enabled in your deployment settings.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131236?
Upgrade to a fixed version: 8.7.0. The vendor's advisory also recommends 8.7.0 or higher or later.
Source: cve.now feed data, cve.org
Related
- 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
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
- CVE-2026-131226Search Processing Language (SPL) Injection through Intrusion Search Dashboard Drilldowns in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.