Quick answers
- Is CVE-2026-76356 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76356 being exploited in the wild.
- How severe is CVE-2026-76356?
- High severity, with a CVSS score of 8.1, published 19 August 2026.
- Which products and versions are affected?
- Splunk SOAR below 8.6.0.
- Is there a fix for CVE-2026-76356?
- 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-76356 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-76356?
- 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
The vulnerability is an authentication bypass (CWE-290) in the Automation Broker notification endpoint of Splunk SOAR versions below 8.6.0. The root cause is that the Automation Broker trusts client-supplied source IP address headers as proof of local system origin, allowing an attacker to forge requests. No authentication or role assignment is required; an unauthenticated user can craft a request with a spoofed IP header to the notification endpoint and achieve arbitrary code execution (RCE) on the SOAR host. The attack is network-accessible with high complexity (CVSS AV:N/AC:H). Splunk addressed this vulnerability by releasing SOAR 8.6.0 and later.
Affected products
- Splunk SOAR below 8.6.0
Timeline
- 2026-08-19: disclosed