In Splunk SOAR versions below 8.8.0, an authenticated user with permission to author and run playbooks could view
Source GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:21 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Splunk SOAR to 8.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk SOAR | Affected
| Fixed in
|
AI-suggested
Since this affects versions below 8.8.0, upgrading to version 8.8.0 or later is recommended if such a version includes a fix. Until a fix is confirmed, restrict playbook authoring and execution permissions to trusted users only to limit exposure.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to author and run playbooks can access action data beyond their authorized scope and modify the status and message of other playbook runs. This occurs due to insufficient authorization checks in the playbook API.