Skip to main content
CVE-2026-131269VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could cause Splunk SOAR to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131269· 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:33 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

If you cannot patch yet, restrict the Apps edit permission to trusted users only to minimize risk.

Description

Splunk SOAR versions prior to 8.8.0 contain a vulnerability where users with the Apps edit permission role can trigger arbitrary code execution on the host by validating an installed app. This occurs because the app validation process does not properly isolate untrusted code from the trusted environment, allowing malicious code execution.

References

Community reviews

Loading reviews…