CVE-2026-76370: In Splunk SOAR versions below 8.6.0, an authenticated user with restricted tenant access could use the Representational State Transfer (REST) API to
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 8.6.0 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- 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: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 18 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
If you cannot patch yet, restrict access to the REST API to trusted users only and monitor for unusual access patterns. Review and enforce strict role-based access controls in multi-tenant deployments. Follow Splunk's documentation on REST roles and permissions and multi-tenant configuration best practices.
Description
Splunk SOAR versions below 8.6.0 contain a vulnerability where an authenticated user with restricted tenant access can use the REST API to view tenant names and identifiers outside their role scope. This occurs because role-based tenant restrictions are not enforced properly in multi-tenant deployments when returning tenant information via the REST API.