Skip to main content
VulnerabilityPublished

CVE-2026-131277: Splunk SOAR · The software uses external input to construct a pathname that is intended to identify a file or

Affects Splunk SOARSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:22 UTC

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

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. Until then, restrict playbook and repository edit permissions to trusted users only. Review and validate playbooks before saving them in the Visual Playbook Editor to ensure no unauthorized modifications to utility blocks are present.

Description

Splunk SOAR versions prior to 8.8.0 contain a vulnerability where users with permission to edit playbooks and repositories can insert a modified utility block that alters REST API delete request paths. When another user with permission to edit playbook code opens and saves the playbook, subsequent runs may delete resources outside the intended scope if the running user has delete permissions. This occurs because the software does not restrict utility blocks from modifying REST API request paths. The issue is fixed in version 8.8.0.

References

Community reviews

Loading reviews…