Description
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view, edit, and run playbooks and access to at least one container label could retrieve a callback handle from a playbook run outside the container-label scope granted to that account.
The vulnerability is possible because Splunk SOAR does not verify that the requested callback handle belongs to the parent playbook run that launched the child playbook.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Data access automation API (https://help.splunk.com/en/splunk-soar/soar-on-premises/python-playbook-api-reference/8.8.0/automation-api/data-access-automation-api) in the Splunk documentation.
The vulnerability is possible because Splunk SOAR does not verify that the requested callback handle belongs to the parent playbook run that launched the child playbook.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Data access automation API (https://help.splunk.com/en/splunk-soar/soar-on-premises/python-playbook-api-reference/8.8.0/automation-api/data-access-automation-api) in the Splunk documentation.
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 view, edit, and run playbooks and access to at least one container label could retrieve a callback handle from a playbook run outside the container-label scope granted to that account. The vulnerability is possible because Splunk SOAR does not verify that the requested callback handle belongs to the parent playbook run that launched the child playbook. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Data access automation API (https://help.splunk.com/en/splunk-soar/soar-on-premises/python-playbook-api-reference/8.8.0/automation-api/data-access-automation-api) in the Splunk documentation. | |
| Title | Improper Access Control in Child Playbook Callback Handles in Splunk SOAR | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T20:37:53.104Z
Reserved: 2026-11-17T20:26:14.306Z
Link: CVE-2026-131249
No data.
Status : Received
Published: 2026-11-19T20:17:39.913
Modified: 2026-11-19T21:17:56.300
Link: CVE-2026-131249
No data.
OpenCVE Enrichment
No data.
Weaknesses
-
CWE-639
Authorization Bypass Through User-Controlled Key