In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could read or
Source GCVE Database
Not known to be exploited · CVSS 8.3 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:20 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.3 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation 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
If you cannot patch yet, restrict playbook edit and run permissions to trusted users only to minimize risk.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permission to edit and run playbooks can access or modify persisted playbook run data beyond their authorized scope. This includes sensitive data such as playbook inputs, outputs, secrets, and intermediate results. The flaw arises because the playbook automation APIs do not enforce data operation restrictions tied to the active playbook run. This can lead to unauthorized data disclosure and corruption of playbook run results.