Skip to main content
VulnerabilityPublished

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

Data as of 19 Nov 2026, 20:21 UTC

CVSS 3.1 base score
8.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.18.1
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:H/PR:N/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 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 by properly binding external user accounts to their provisioning identity providers and verifying provider ownership during authentication.

Description

CVE-2026-131297 is a vulnerability in Splunk SOAR versions prior to 8.8.0 that allows an operator of one configured external identity provider to authenticate as a user associated with a different identity provider. This occurs because Splunk SOAR does not bind external user accounts to their provisioning identity provider and authenticates solely by username without verifying provider ownership. Exploiting this requires multiple configured identity providers with distinct trust domains and a target username accessible through a different provider. If the targeted account has the Administrator role, the attacker could gain full control over the Splunk SOAR deployment. The issue is fixed in version 8.8.0.

References

Community reviews

Loading reviews…