CVE-2026-131252: Splunk SOAR · The software does not perform an authorization check when an actor attempts to access a resource or
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 20:41 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 Splunk SOAR to version 8.8.0 or later, where the vulnerability is fixed. No other mitigations are specified or required as the fix addresses the authorization check deficiency.
Description
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where users with Assets edit or delete permissions can modify or delete assets across tenants without proper tenant access verification. This flaw allows unauthorized changes to assets belonging to other tenants via the REST API, potentially exposing credentials and disrupting integrations. The issue arises because the software checks only for permission to edit or delete assets but does not confirm tenant access rights before performing these actions. The vulnerability is fixed in version 8.8.0.