Skip to main content
VulnerabilityPublished

CVE-2026-131287: Splunk SOAR · The software performs an authorization check when an actor attempts to access a resource or perform

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 8.8.0 as a priority.

Data as of 19 Nov 2026, 20:21 UTC

CVSS 3.1 base score
9.6Critical
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.19.6
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H

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

AI-suggested

Upgrade Splunk SOAR to version 8.8.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Users should apply the official patch promptly to prevent exploitation.

Description

CVE-2026-131287 is a critical vulnerability in Splunk SOAR versions prior to 8.8.0. It allows users with roles that have Playbooks view, edit, execute, and delete permissions to cause cross-repository playbook references to execute attacker-controlled playbook code. This occurs because Splunk SOAR can rebind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused. The vulnerability is fixed in version 8.8.0.

References

Community reviews

Loading reviews…