Skip to main content
CVE-2026-131263VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, a user that holds a role with only the apps:edit permission could install a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131263· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 8.8.0 soon.

Data as of 19 Nov 2026, 22:34 UTC

CVSS 3.1 base score
8.8High
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.18.8
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 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

A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or above to remediate this vulnerability. Until upgraded, restrict roles with the apps:edit permission to trusted users only. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes.

Description

In Splunk SOAR versions below 8.8.0, a user with a role limited to the apps:edit permission can exploit a vulnerability to install a connector app that writes attacker-controlled files outside the intended app directory. This allows modification of files used by Splunk SOAR and execution of arbitrary code with the privileges of the Splunk SOAR user account. The issue arises because the dependency installation command is constructed from app metadata without proper validation, enabling argument manipulation.

References

Community reviews

Loading reviews…