Skip to main content
CVE-2026-131281VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, a user with asset edit permission could change the approval requirements and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131281· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.8.0 when convenient.

Data as of 19 Nov 2026, 22:22 UTC

CVSS 3.1 base score
4.3Medium
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.14.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: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 19 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

AI-suggested

If you cannot patch yet, organizations should carefully control and monitor users with asset edit permissions to mitigate risk.

Description

In Splunk SOAR versions prior to 8.8.0, users with asset edit permissions can modify approval requirements and the effective automation user for an asset without these changes being recorded in field-level audit logs. This lack of audit coverage reduces accountability and weakens investigation capabilities for changes made to security-sensitive asset settings.

References

Community reviews

Loading reviews…