CVE-2026-131259: 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 5.4 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 20:49 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
Upgrade Splunk SOAR to version 8.8.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.
Description
In Splunk SOAR versions below 8.8.0, a user with permission to create and view containers for a label could use the Representational State Transfer (REST) API to create a container that references a workbook phase in a case the user cannot view, disclosing the phase name and creating an inconsistent phase association. The vulnerability exists because the Container REST API does not enforce the same case-scoped authorization when it accepts a workbook-phase reference during container creation.