Splunk · Splunk SOAR · CWE-863 · published 2026-11-19
CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-131287 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 27% of all CVEs. This Splunk SOAR vulnerability: CVSS 9.6 (v3.1), a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (28th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.6 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-863: Incorrect Authorization
Affected versions (from the CVE record)#
- Splunk Splunk SOAR
0to before8.8.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.