In Splunk SOAR versions below 8.8.0, an authenticated Splunk SOAR user with permission to edit and run playbooks could read action status and callback state from a playbook run outside the authorized container-label or tenant scope for that user.
The vulnerability is possible because the playbook API uses mutable runtime context to identify a playbook run instead of preserving the server-provided context.
Advisories

No advisories yet.

Fixes

Solution

Upgrade Splunk SOAR to version 8.8.0 or higher.


Workaround

No workaround given by the vendor.

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 Splunk SOAR user with permission to edit and run playbooks could read action status and callback state from a playbook run outside the authorized container-label or tenant scope for that user. The vulnerability is possible because the playbook API uses mutable runtime context to identify a playbook run instead of preserving the server-provided context.
Title Authorization Bypass in the REST API in Splunk SOAR
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-11-19T19:56:12.934Z

Reserved: 2026-11-17T20:26:14.306Z

Link: CVE-2026-131247

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-19T20:17:39.670

Modified: 2026-11-19T20:17:39.670

Link: CVE-2026-131247

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses