Skip to main content
CVE-2026-76365VulnerabilityPublished

In Splunk SOAR versions below 8.6.0, a user who holds the "Automation Engineer" Splunk SOAR role could run arbitrary

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76365· Medium 6.5

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

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% 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: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 18 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

A fix is available in Splunk SOAR version 8.6.0 and later. Users should upgrade to version 8.6.0 or above to remediate this vulnerability. Until then, restrict the Automation Engineer role to trusted users only. No vendor advisory or patch links were provided, so verify the patch status with official Splunk documentation.

Description

Splunk SOAR versions below 8.6.0 contain a SQL injection vulnerability that allows users with the "Automation Engineer" role to execute arbitrary SQL statements on the Splunk SOAR database via custom list retrieval in playbooks. This flaw enables create, read, update, and delete operations on the database due to improper handling of the list name parameter in SQL queries.

References

Community reviews

Loading reviews…