CVE-2026-76359: Splunk SOAR · The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
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.5% chance of exploitation in 30 days – higher than 44% 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:N/I:H/A:HExploitation 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
A fix is available in Splunk SOAR version 8.6.0. Users should upgrade to version 8.6.0 or later to remediate this vulnerability. No additional mitigation steps are indicated in the vendor advisory.
Description
CVE-2026-76359 is a path traversal vulnerability in Splunk SOAR versions prior to 8.6.0. It allows a user with Administrator privileges to exploit the Universal Forwarder installer's archive extraction process to write files outside the intended installation directory. This occurs because the extraction workflow does not properly verify that archive members remain within the designated destination directory. The vulnerability can lead to unauthorized file writes, impacting system integrity and availability.