In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:20 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or above to remediate this vulnerability. No other mitigation or workaround is indicated.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to author and run playbooks can add messages to the log of a different playbook run, potentially causing that run to fail. This includes runs outside the labels the user is authorized to access. The issue arises because the product does not verify that playbook API requests use the trusted runtime context for the current playbook run.