CVE-2026-131289: Splunk SOAR · The software does not sufficiently verify the origin or authenticity of data,
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 20:21 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 3.1 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:H/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
A fix for this vulnerability is available in Splunk SOAR version 8.8.0. Users should upgrade to version 8.8.0 or later to remediate this issue. No additional mitigation steps are indicated by the vendor advisory.
Description
Splunk SOAR versions prior to 8.8.0 contain a vulnerability where users with permissions to edit and run playbooks can cause the system to execute non-read-only actions from a Safe Mode playbook. This occurs because the software does not properly verify that the playbook run context in an action request matches the server-provided context, potentially leading to unauthorized state changes.