CVE-2026-76527: Splunk SOAR improper handling of exceptional conditions

CVE-2026-76527 · Severity: info · Published 2026-10-21

Splunk SOAR, a platform that automates security incident response, contains a flaw in how it handles error conditions. This vulnerability could allow attackers to trigger unexpected behavior in the system, potentially disrupting automated security operations or exposing sensitive data during error states.

Technologies: Splunk SOAR. Vendors: Splunk.

Quick answers

Is CVE-2026-76527 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-76527 being exploited in the wild.
How severe is CVE-2026-76527?
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-76527?
Yes: fixed in Splunk SOAR 8.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-76527 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-76527?
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

Technical details

CVE-2026-76527 involves improper check or handling of exceptional conditions (CWE-703) in Splunk SOAR. The vulnerability has a CVSS score of 5.5, indicating a moderate-severity flaw where error handling logic fails to properly validate or manage exceptional states, potentially allowing network-based exploitation without authentication.

Affected products

  • Splunk SOAR Below 8.7.0

Timeline

  • 2026-10-21: disclosed
  • 2026-10-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.