Quick answers
- Is CVE-2026-76530 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76530 being exploited in the wild.
- How severe is CVE-2026-76530?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Splunk SOAR Below 8.7.0.
- Is there a fix for CVE-2026-76530?
- Yes: fixed in Splunk SOAR 8.7.0 or higher. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76530 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-76530?
- 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.
How to fix
- Fixed in: Splunk SOAR 8.7.0 or higher
Technical details
This vulnerability (CWE-647) involves improper authorization decisions based on URL path canonicalization. An attacker can craft non-canonical URL paths (such as those containing encodings, redundant slashes, or path traversal sequences) that are processed differently by the authorization logic compared to the actual resource handler, allowing access to restricted functionality. The flaw affects Splunk SOAR versions below 8.7.0 and is exploitable via network access without requiring user interaction.
Affected products
- Splunk SOAR Below 8.7.0
Timeline
- 2026-10-21: disclosed
- 2026-10-21: advisory: SVD-2026-1011