CVE-2026-76368: Splunk SOAR · The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 2.7 Low : upgrade to 8.6.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% 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:H/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk SOAR | Affected
| Fixed in
|
AI-suggested
Upgrade to Splunk SOAR version 8.6.0 or later where this authorization check issue is fixed. Since the vulnerability affects versions prior to 8.6.0, applying the official update is the recommended remediation. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76368 is a low-severity vulnerability in Splunk SOAR versions prior to 8.6.0 where users with the playbooks:view permission can view metadata about playbook repositories they are not authorized to access. This occurs because the Playbook History feature does not verify repository permissions before returning playbook revision metadata.