Skip to main content
VulnerabilityPublished

CVE-2026-76370: Splunk SOAR · The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.6.0 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 17 Nov 2026.

What to do

Upgrade Splunk SOAR to 8.6.0.

Affected software

ProductAffectedFixed in
SplunkSplunk SOARAffected
  • >=8.6 <8.6.0
Fixed in
  • 8.6.0

AI-suggested

Upgrade Splunk SOAR to version 8.6.0 or later, where this authorization check issue is fixed. Since this is an on-premises product, administrators should apply the official update to remediate the vulnerability. No vendor advisory content was provided explicitly stating patch availability, but the affected versions indicate that 8.6.0 is the fixed version.

Description

CVE-2026-76370 is a medium-severity vulnerability in Splunk SOAR versions prior to 8.6.0. It allows an authenticated user with restricted tenant access to bypass role-based tenant restrictions via the REST API, enabling them to view tenant names and identifiers outside their authorized scope in multi-tenant deployments. This occurs because the software does not correctly enforce authorization checks when returning tenant information through the REST API.

References

Community reviews

Loading reviews…