In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to
Source GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:33 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 8.8 |
|---|
- 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:HExploitation 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
Upgrade to Splunk SOAR version 8.8.0 or later where this vulnerability is fixed. Since this is a software vulnerability with a fixed version, applying the official patch is the recommended remediation. No alternative mitigations are specified.
Description
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where an authenticated user with repository edit access can write files outside the configured repository. This occurs because the software does not enforce repository paths to remain within the configured repository boundaries, allowing modification of files accessible by the Splunk SOAR user account.