CVE-2026-131284: Splunk SOAR · The software receives input from an upstream component that specifies multiple attributes,
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 20: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 18 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 Splunk SOAR to version 8.8.0 or later, where this vulnerability is fixed. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-131284 affects Splunk SOAR versions prior to 8.8.0. An authenticated user with permissions to view and edit containers can import a container archive that causes artifacts to appear incorrectly associated with cases or notes. This discrepancy arises because the import process accepts artifact workflow state from the archive rather than deriving it from actual case and note associations. This can lead to REST API clients and filters using inaccurate artifact states.