Authorization Bypass in Splunk SOAR Playbook Status
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, 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
|