Quick answers
- Is CVE-2026-76362 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76362 being exploited in the wild.
- How severe is CVE-2026-76362?
- High severity, with a CVSS score of 7.4, published 19 August 2026.
- Which products and versions are affected?
- Splunk SOAR below 8.6.0.
- Is there a fix for CVE-2026-76362?
- A patch was published on 2026-08-19: Fix released in Splunk SOAR 8.6.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76362 attacked?
- It is attacked over the network or from the adjacent network.
- Am I affected by CVE-2026-76362?
- 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
This vulnerability is an improper certificate validation flaw (CWE-295) in Splunk SOAR's CyberArk Vault Privileged Access Manager (PAM) REST client integration. The CyberArk REST client does not verify server certificates by default, making it vulnerable to man-in-the-middle (MITM) attacks. An unauthenticated attacker with network-path interception capability between Splunk SOAR and the configured CyberArk REST server can observe, intercept, and modify all credential data exchanged through that credential manager. The attack requires the attacker to be on the network path between SOAR and the CyberArk server. Splunk released a fix in version 8.6.0; affected versions are below 8.6.0. Additional remediation steps beyond upgrading are required.
Affected products
- Splunk SOAR below 8.6.0
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fix released in Splunk SOAR 8.6.0