Skip to main content
VulnerabilityPublished

CVE-2026-131274: Splunk SOAR · When a security-critical event occurs, the software either does not record the event or omits

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 8.8.0 when convenient.

Data as of 19 Nov 2026, 20:19 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.12.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
SplunkSplunk SOARAffected
  • <8.8.0
Fixed in
  • 8.8.0

Description

In Splunk SOAR versions below 8.8.0, a user with the system_settings permission could change event custom field definitions without the changes appearing in the audit trail, reducing forensic visibility and change accountability. The issue occurs because Splunk SOAR does not audit custom field definition changes.

References

Community reviews

Loading reviews…