Improper Access Control through Playbooks in Splunk SOAR
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Splunk | Splunk SOAR | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade Splunk SOAR to version 8.8.0 or higher.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1108 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a different playbook run log and cause that run to fail, including runs outside the labels that the user could access. The vulnerability is possible because Splunk SOAR does not verify that playbook API requests use the trusted runtime context for the current playbook run. | |
| Title | Improper Access Control through Playbooks in Splunk SOAR | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|