Quick answers
- Is CVE-2026-76368 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76368 being exploited in the wild.
- How severe is CVE-2026-76368?
- 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-76368?
- A patch was published on 2026-08-19: Fix available 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-76368 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76368?
- 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 a missing authorization check (CWE-862) in the Playbook History component of Splunk SOAR. When a user holds a role with the playbooks:view permission, the Playbook History endpoint returns revision metadata without verifying that the user has authorization to access the specific playbook repository. The vulnerability requires an authenticated user with at least the playbooks:view permission; exploitation results in unauthorized disclosure of playbook repository metadata. The fix is available in Splunk SOAR 8.6.0 and later.
Affected products
- Splunk SOAR below 8.6.0
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fix available in Splunk SOAR 8.6.0