The vulnerability is possible because the Playbook Automation API accepts a supplied playbook run identifier without verifying that it is bound to the server-provided playbook execution context.
The vulnerability requires a running playbook on a container label that the user cannot view.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade Splunk SOAR to version 8.8.0 or higher.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1108 |
|
Fri, 20 Nov 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk
Splunk splunk |
|
| Vendors & Products |
Splunk
Splunk splunk |
Thu, 19 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk SOAR versions below 8.8.0, a Splunk SOAR user who can edit and run playbooks for a permitted container label could associate action and callback state with a running playbook outside that container label. This could affect playbook automation for containers that the user cannot view. The vulnerability is possible because the Playbook Automation API accepts a supplied playbook run identifier without verifying that it is bound to the server-provided playbook execution context. The vulnerability requires a running playbook on a container label that the user cannot view. | |
| Title | Authorization Bypass through the REST API in Splunk SOAR | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T21:19:34.565Z
Reserved: 2026-11-17T20:26:14.311Z
Link: CVE-2026-131291
No data.
Status : Received
Published: 2026-11-19T20:17:45.153
Modified: 2026-11-19T22:18:03.037
Link: CVE-2026-131291
No data.
OpenCVE Enrichment
Updated: 2026-11-20T11:00:10Z
-
CWE-639
Authorization Bypass Through User-Controlled Key