In Splunk SOAR versions below 8.8.0, a user with permission to create containers on one label could use the Representational State Transfer (REST) API to create a container with a parent relationship to a container that the user cannot access. This could let the user alter incident lineage across authorization boundaries and identify existing restricted containers.
The vulnerability is possible because the REST API accepts a customer-supplied parent relationship when creating a container without authorizing access to the referenced container.
For more information see REST Containers (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.6.0/container-endpoints/rest-containers) and 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) in the Splunk documentation.
The vulnerability is possible because the REST API accepts a customer-supplied parent relationship when creating a container without authorizing access to the referenced container.
For more information see REST Containers (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.6.0/container-endpoints/rest-containers) and 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) in the Splunk documentation.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
Upgrade Splunk SOAR to version 8.8.0 or higher.
Workaround
No workaround given by the vendor.
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, a user with permission to create containers on one label could use the Representational State Transfer (REST) API to create a container with a parent relationship to a container that the user cannot access. This could let the user alter incident lineage across authorization boundaries and identify existing restricted containers. The vulnerability is possible because the REST API accepts a customer-supplied parent relationship when creating a container without authorizing access to the referenced container. For more information see REST Containers (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.6.0/container-endpoints/rest-containers) and 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) in the Splunk documentation. | |
| Title | Improper Access Control through the REST API in Splunk SOAR | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: cisco
Published:
Updated: 2026-11-19T20:37:45.517Z
Reserved: 2026-11-17T20:26:14.307Z
Link: CVE-2026-131254
No data.
Status : Received
Published: 2026-11-19T20:17:40.537
Modified: 2026-11-19T20:17:40.537
Link: CVE-2026-131254
No data.
OpenCVE Enrichment
No data.
Weaknesses