CVE-2026-131281: Splunk SOAR · When a security-critical event occurs, the software either does not record the event or omits
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 to Splunk SOAR version 8.8.0 or later, where this vulnerability is fixed. The vendor has provided an official fix in version 8.8.0. Until the upgrade is applied, organizations should be aware that audit logs may not fully capture changes to asset approval voting fields and effective automation user fields.
Description
Splunk SOAR versions prior to 8.8.0 have a vulnerability where changes to certain security-sensitive asset settings are not fully recorded in audit logs. Specifically, users with asset edit permissions can modify approval requirements and the effective automation user for an asset without these changes being captured at the field level. This lack of detailed audit logging can reduce accountability and hinder investigations into changes made to critical asset configurations.