Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to create containers on one label can create a container referencing a parent container they cannot access. This allows alteration of incident lineage across authorization boundaries and identification of restricted containers. The issue arises because the REST API accepts a user-supplied parent container without verifying access permissions to that container.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an unauthenticated user can gain administrator privileges by exploiting a flaw in the user-management REST API. The issue arises because the API incorrectly interprets numeric role names as role identifiers, allowing privilege escalation through role assignment.
In Splunk SOAR versions below 8.8.0, a user with permission to view and modify containers labeled as allowed can add artifacts to containers they are not authorized to view or modify. This occurs due to improper enforcement of authorization boundaries in the REST API artifact-creation workflow.
Splunk SOAR versions below 8.8.0 contain a vulnerability where users with System Settings edit permission and restricted tenant access can modify settings of tenants outside their scope via the REST API. This flaw arises because the Tenant REST API verifies the edit permission but fails to enforce tenant restrictions, allowing unauthorized access to tenant configurations. Exploitation could lead to exposure of confidential tenant data, unauthorized changes to tenant settings and automation, or disruption of tenant operations.
In Splunk SOAR versions below 8.8.0, a user with edit permission on the container label of a pending external prompt can access the external prompt link via the REST API. This link allows the user to view and resolve the associated approval, bypassing intended approval scope restrictions. The vulnerability arises because the approval detail REST API exposes the external prompt link in responses beyond the assigned approval scope.
In Splunk SOAR versions below 8.8.0, an authenticated user with permissions to edit and run playbooks could access action status and callback state information from playbook runs outside their authorized container-label or tenant scope. This occurs due to the playbook API using mutable runtime context rather than preserving server-provided context to identify playbook runs.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to edit and run playbooks can modify a child playbook callback handle associated with another playbook run. This occurs because the Playbook API does not verify that callback-handle updates belong to the related parent and child playbook runs, potentially altering the callback behavior of that run.
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to edit containers for an allowed label can forge the author attribution of container pins and access user details beyond their authorization. This occurs because the Container Pin REST API does not properly restrict caller-provided author fields, allowing reassignment of pin authors and unauthorized querying of user-related data.
In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on the container label of a pending approval can exploit a vulnerability in the Approval details REST API. This flaw allows the user to read an external-prompt capability without verifying approval ownership, enabling them to view prompt content, alter the pending approval decision, and modify action parameters.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permissions to view, edit, and run playbooks and access at least one container label can retrieve a callback handle from a playbook run outside their container-label scope. This occurs because the system does not verify that the callback handle belongs to the parent playbook run that launched the child playbook. The vulnerability has a CVSS score of 4.3, indicating medium severity.
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to view a container can access the REST API to retrieve a live external prompt link for approvals belonging to other users. This link allows reading and responding to approval prompts without further authentication, potentially disrupting automated workflows.
Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where a user with the run_collect capability can inject attacker-controlled values into the Weak Encrypted Communication report. This can lead to another user executing attacker-controlled SPL commands with their permissions when interacting with the report's drilldown feature. The flaw arises from insufficient validation of certain report data before use in drilldown searches.
In Splunk SOAR versions below 8.8.0, a vulnerability exists where users with edit permissions on containers limited to certain container labels could modify container pins outside their authorized labels. This occurs due to insufficient enforcement of container label authorization boundaries in the Container Pin REST API.
In Splunk SOAR versions below 8.8.0, an authenticated user can cause the system to store excessive data in the Ingestion Status history via the REST API. This occurs because there is no limit on the amount of request data recorded for failed container creation attempts. When another user with permission to view system settings accesses this history, the large stored data can cause increased resource usage and degrade the availability of administrative monitoring.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into Updates data. When another user with access to the System Update Status report selects an affected row, Splunk may execute attacker-controlled Search Processing Language (SPL) commands with the selecting user's permissions. This occurs because the report does not validate certain input fields before using them in drilldown searches, potentially allowing unauthorized data access and modification.
In Splunk SOAR versions below 8.8.0, users with a role granting the containers:view permission could access automation history for containers beyond their assigned label or tenant scope. This exposure includes action parameters, connector result summaries, and other investigation and response activities. The issue arises because the REST API checks container view permissions but does not enforce scope restrictions on automation history access.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can store attacker-controlled certificate values. When another user with access to the Secure Sockets Layer Search dashboard selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard encodes certificate values for drilldown links but does not properly escape them as SPL search literals. This flaw can lead to unauthorized data access and modification by the user who initially stored the malicious values.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into data used by the Credit Card Data Found dashboard. When another user with access to this dashboard selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard does not validate source and destination values before using them in drilldown searches, potentially exposing sensitive data accessible to the selecting user.
In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user who can influence indexed event data may cause the system to execute attacker-controlled Search Processing Language (SPL) commands when an authenticated user interacts with certain workflow actions. This occurs because the affected workflow actions insert event-field values directly into searches without proper validation or quoting. Exploitation could allow unauthorized access or modification of sensitive data and disruption of services for the authenticated user. The vulnerability is tracked as CVE-2026-131236 with a high severity rating.
In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where users with the run_collect capability can inject attacker-controlled values into vulnerability scan data. When another user accesses the Vulnerability Scan Details dashboard and selects these values, Splunk may execute attacker-controlled Search Processing Language (SPL) commands with the selecting user's permissions. This occurs because the dashboard does not validate destination values before using them in drilldown searches, potentially allowing unauthorized data access and modification.