In Splunk SOAR versions below 8.8.0, a user who can edit and run a playbook on a permitted label could cause Splunk
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:21 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the affected versions are below 8.8.0, upgrading to version 8.8.0 or later is implied to remediate the issue. Until then, restrict playbook editing and running permissions to trusted users only. Monitor vendor advisories for official patches or updates.
Description
In Splunk SOAR versions below 8.8.0, a vulnerability exists where a user with permissions to edit and run a playbook on a permitted label can cause the system to return custom-function status and callback state from a different playbook run. This occurs due to insufficient binding between the custom-function-status request and the initiating playbook run.