Skip to main content
VulnerabilityPublished

CVE-2026-131291: Splunk SOAR · The system's authorization functionality does not prevent one user from gaining access to another

Affects Splunk SOARSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:21 UTC

CVSS 3.1 base score
6.5Medium
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.5
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 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 mitigations are specified. Since the vulnerability requires a running playbook on an unauthorized container label, restricting playbook creation and execution privileges may reduce exposure but upgrading is the definitive remediation.

Description

CVE-2026-131291 is a vulnerability in Splunk SOAR versions prior to 8.8.0 where a user with permissions to edit and run playbooks for a specific container label can manipulate playbook automation for containers they are not authorized to view. This occurs because the Playbook Automation API does not verify that a supplied playbook run identifier matches the server's playbook execution context. The issue requires an existing running playbook on an unauthorized container label.

References

Community reviews

Loading reviews…