{"api_version":"1","generated_at":"2026-11-19T20:42:35+00:00","cve":"CVE-2026-131287","urls":{"html":"https://cve.report/CVE-2026-131287","api":"https://cve.report/api/cve/CVE-2026-131287.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-131287","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-131287"},"summary":{"title":"Remote Code Execution (RCE) through the REST API in Splunk SOAR","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.\nThe 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.","state":"PUBLISHED","assigner":"cisco","published_at":"2026-11-19 20:17:44","updated_at":"2026-11-19 20:17:44"},"problem_types":["CWE-863","CWE-863 The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions."],"metrics":[{"version":"3.1","source":"psirt@cisco.com","type":"Primary","score":"9.6","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","baseScore":9.6,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"9.6","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","data":{"baseScore":9.6,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1108","name":"https://advisory.splunk.com/advisories/SVD-2026-1108","refsource":"psirt@cisco.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-131287","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-131287","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Splunk","product":"Splunk SOAR","version":"affected 8.8.0 custom","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade Splunk SOAR to version 8.8.0 or higher.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"Splunk SOAR","vendor":"Splunk","versions":[{"lessThan":"8.8.0","status":"affected","version":"0","versionType":"custom"}]}],"datePublic":"2026-11-18T00:00:00.000Z","descriptions":[{"lang":"en","value":"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.\nThe 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."}],"metrics":[{"cvssV3_1":{"baseScore":9.6,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-863","description":"The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.","lang":"en","type":"cwe"}]}],"providerMetadata":{"dateUpdated":"2026-11-19T19:56:36.074Z","orgId":"d1c1063e-7a18-46af-9102-31f8928bc633","shortName":"cisco"},"references":[{"url":"https://advisory.splunk.com/advisories/SVD-2026-1108"}],"solutions":[{"lang":"en","value":"Upgrade Splunk SOAR to version 8.8.0 or higher."}],"source":{"advisory":"SVD-2026-1108","discovery":""},"title":"Remote Code Execution (RCE) through the REST API in Splunk SOAR"}},"cveMetadata":{"assignerOrgId":"d1c1063e-7a18-46af-9102-31f8928bc633","assignerShortName":"cisco","cveId":"CVE-2026-131287","datePublished":"2026-11-19T19:56:36.074Z","dateReserved":"2026-11-17T20:26:14.311Z","dateUpdated":"2026-11-19T19:56:36.074Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-19 20:17:44","lastModifiedDate":"2026-11-19 20:17:44","problem_types":["CWE-863","CWE-863 The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions."],"metrics":{"cvssMetricV31":[{"source":"psirt@cisco.com","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","baseScore":9.6,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.1,"impactScore":5.8}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"131287","Ordinal":"1","Title":"Remote Code Execution (RCE) through the REST API in Splunk SOAR","CVE":"CVE-2026-131287","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"131287","Ordinal":"1","NoteData":"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.\nThe 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.","Type":"Description","Title":"Remote Code Execution (RCE) through the REST API in Splunk SOAR"}]}}}