Quick answers
- Is CVE-2026-76369 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76369 being exploited in the wild.
- How severe is CVE-2026-76369?
- Low severity, with a CVSS score of 2.7, published 19 August 2026.
- Which products and versions are affected?
- Splunk SOAR below 8.6.0.
- Is there a fix for CVE-2026-76369?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-76369 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76369?
- Check whether you run Splunk SOAR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the Automation Broker log upload functionality in Splunk SOAR versions prior to 8.6.0. The vulnerability arises because the log upload feature accepts user-controlled filename input without proper validation or sanitization before writing files to disk. An attacker with the OnPrem Broker role can craft filenames containing path traversal sequences (e.g., "../") to write files outside the intended log directory. This requires authentication with the OnPrem Broker role and network access to the Automation Broker endpoint. The attack allows arbitrary file writes to the filesystem, potentially enabling configuration tampering or privilege escalation. The fix is available in version 8.6.0 and higher.
Affected products
- Splunk SOAR below 8.6.0
Timeline
- 2026-08-19: disclosed