Description
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could view child playbook status and loop-state metadata for playbook runs outside the authorized scope for that user.
The vulnerability is possible because the playbook status API does not bind the requested run to the current execution context before it returns metadata.
The vulnerability is possible because the playbook status API does not bind the requested run to the current execution context before it returns metadata.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
Vendor Solution
Upgrade Splunk SOAR to version 8.8.0 or higher.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1108 |
|
History
Thu, 19 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could view child playbook status and loop-state metadata for playbook runs outside the authorized scope for that user. The vulnerability is possible because the playbook status API does not bind the requested run to the current execution context before it returns metadata. | |
| Title | Authorization Bypass in Splunk SOAR Playbook Status | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T19:56:37.881Z
Reserved: 2026-11-17T20:26:14.311Z
Link: CVE-2026-131290
No data.
Status : Received
Published: 2026-11-19T20:17:45.027
Modified: 2026-11-19T20:17:45.027
Link: CVE-2026-131290
No data.
OpenCVE Enrichment
No data.
Weaknesses