Quick answers
- Is CVE-2026-76306 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76306 being exploited in the wild.
- How severe is CVE-2026-76306?
- High severity, with a CVSS score of 7.5, published 21 October 2026.
- Which products and versions are affected?
- Splunk SOAR below 8.7.0.
- Is there a fix for CVE-2026-76306?
- Yes: fixed in 8.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76306 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-76306?
- 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: 8.7.0
Technical details
The vulnerability stems from Splunk SOAR applying REST API query filters to user records before sensitive fields such as password hashes and authorization tokens are protected from query processing. An attacker with the Observer role can craft specific REST API queries to infer these credentials through response patterns. This requires network access and authentication as a low-privileged user, but does not require user interaction.
Affected products
- Splunk SOAR below 8.7.0
Timeline
- 2026-10-21: disclosed
- 2026-10-21: patched