{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131287 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-131287 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131287 is a critical vulnerability in Splunk SOAR, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-131287 and fix it if it is affected.\n\nWhat it is: CVE-2026-131287 is a critical vulnerability in Splunk SOAR, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-131287 in the wild and no public exploit code.\n\nAffected product: Splunk SOAR. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-131287/ (Markdown: https://insights.sbomify.com/CVE-2026-131287/index.md)","id":"CVE-2026-131287","markdown":"https://insights.sbomify.com/CVE-2026-131287/index.md","name":"CVE-2026-131287","record":{"aliases":["GHSA-j246-7c6p-q2vm"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","component":null,"cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Remote Code Execution (RCE) through the REST API in Splunk SOAR","id":"CVE-2026-131287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"[Flashpoint] Privilege Escalation through HAProxy Cluster Operations in Splunk SOAR","id":"CVE-2026-131288"},"nickname":null,"packages":[],"prev":{"headline":"Improper Access Control through the REST API in Splunk SOAR","id":"CVE-2026-131286"},"products":["Splunk SOAR"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-131287/"}