In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the
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:39 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:L/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
A fixed version is available starting with Splunk SOAR 8.8.0. Users should upgrade to version 8.8.0 or later to remediate this issue. No other mitigation or workaround is indicated in the vendor documentation.
Description
Splunk SOAR versions below 8.8.0 contain a vulnerability where a user with permission to edit containers for an allowed label can forge the author attribution of container pins and access user details beyond their authorization. This occurs because the Container Pin REST API does not properly restrict caller-provided author fields, allowing reassignment of pin authors and unauthorized querying of user-related data.