CVE-2026-76366: Splunk SOAR · The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.6.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:H/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
Since the vulnerability affects versions prior to 8.6.0, upgrading to version 8.6.0 or later may mitigate the issue if confirmed by the vendor. Until then, restrict access to trusted users and monitor for unusual API activity.
Description
CVE-2026-76366 is a medium severity vulnerability in Splunk SOAR versions before 8.6.0. It allows a user with a valid account to exploit REST API filtering on playbook runs to retrieve session tokens. These tokens can expose all data accessible to the affected user. The issue arises because the REST API does not properly block filters from matching values that should be hidden in responses. This vulnerability affects versions prior to 8.6.0.