CVE-2026-76357: 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 7.6 High : upgrade to 8.6.0 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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:L/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
The vulnerability affects Splunk SOAR versions below 8.6.0. Users should upgrade to version 8.6.0 or later where this issue is fixed. Since the product is not a cloud service, remediation requires applying the official patch or upgrade. Check Splunk's official documentation and security advisories for the latest updates and instructions.
Description
CVE-2026-76357 is a high-severity vulnerability in Splunk SOAR versions below 8.6.0. It allows an authenticated user without an assigned role to submit a crafted file path via the REST API, leading to arbitrary code execution. This occurs because the REST API does not require role assignment and fails to restrict file paths to the intended temporary directory.