In Splunk SOAR versions below 8.8.0, a user with asset edit permission could change the approval requirements and
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:22 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 4.3 |
|---|
- 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: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
If you cannot patch yet, organizations should carefully control and monitor users with asset edit permissions to mitigate risk.
Description
In Splunk SOAR versions prior to 8.8.0, users with asset edit permissions can modify approval requirements and the effective automation user for an asset without these changes being recorded in field-level audit logs. This lack of audit coverage reduces accountability and weakens investigation capabilities for changes made to security-sensitive asset settings.