In Splunk SOAR versions below 8.8.0, a user with the system_settings permission could change event custom field
Source GCVE Database
Not known to be exploited · CVSS 2.7 Low : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:34 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 2.7 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:H/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 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
A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or newer to ensure that changes to event custom field definitions are properly audited. Until upgraded, organizations should restrict system_settings permission to trusted administrators and monitor change activities closely. Patch status is confirmed by the fixed version 8.8.0.
Description
Splunk SOAR versions prior to 8.8.0 have a vulnerability where users with system_settings permission can modify event custom field definitions without these changes being recorded in the audit trail. This lack of auditing reduces forensic visibility and accountability for changes made to custom fields.