Skip to main content
CVE-2026-131289VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, a user who holds a role that can edit and run playbooks in Splunk SOAR could

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131289· Low 3.1

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

Data as of 19 Nov 2026, 22:21 UTC

CVSS 3.1 base score
3.1Low
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.13.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: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

Upgrade to Splunk SOAR version 8.8.0 or later where this vulnerability is fixed. Until patched, restrict roles that can edit and run playbooks to trusted users only.

Description

In Splunk SOAR versions below 8.8.0, users with roles that allow editing and running playbooks could exploit a vulnerability to execute non-read-only actions from a Safe Mode playbook, causing unauthorized state changes. This occurs because the system does not verify that the playbook run context in an action request matches the server-provided context.

References

Community reviews

Loading reviews…