CVE-2026-131247: 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 4.3 Medium : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 20:41 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:L/I:N/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
CVE-2026-131247 is a medium severity vulnerability in Splunk SOAR versions before 8.8.0. It allows an authenticated user with permission to edit and run playbooks to read action status and callback state from playbook runs outside their authorized container-label or tenant scope. This occurs because the playbook API relies on mutable runtime context rather than preserving server-provided context for identifying playbook runs. The issue is fixed in version 8.8.0.