CVE-2026-76365: Splunk SOAR · The software constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
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 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% 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:H/I:H/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 16 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
The vulnerability affects Splunk SOAR versions prior to 8.6.0. Users should upgrade to version 8.6.0 or later where this issue is fixed. Until then, restrict the Automation Engineer role to trusted users only.
Description
CVE-2026-76365 is a SQL injection vulnerability in Splunk SOAR versions prior to 8.6.0. A user with the Automation Engineer role can execute arbitrary SQL commands against the Splunk SOAR database via custom list retrieval in playbooks. This allows unauthorized create, read, update, and delete operations on database data. The vulnerability arises because the software improperly constructs SQL queries using externally supplied list names without proper parameterization.