Skip to main content
VulnerabilityPublished

CVE-2026-131262: 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 7.1 High : upgrade to 8.8.0 soon.

Data as of 19 Nov 2026, 20:35 UTC

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

Upgrade Splunk SOAR to version 8.8.0 or later, where this authorization vulnerability is fixed. No other mitigation is required as the vendor has provided an official fix.

Description

Splunk SOAR versions prior to 8.8.0 contain an authorization flaw where authenticated users with permissions to view and edit containers in at least one container label can create artifacts linked to containers and artifacts outside their authorized labels. This flaw allows exposure of fields from restricted artifacts and unauthorized modification of incident lineage. The issue arises because the system does not verify access rights to the parent container and artifact when creating new artifacts. The vulnerability is fixed in version 8.8.0.

References

Community reviews

Loading reviews…