{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131296 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-131296 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131296 is a medium-severity vulnerability in Splunk SOAR, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-131296 and fix it if it is affected.\n\nWhat it is: CVE-2026-131296 is a medium-severity vulnerability in Splunk SOAR, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-131296 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-131296/ (Markdown: https://insights.sbomify.com/CVE-2026-131296/index.md)","id":"CVE-2026-131296","markdown":"https://insights.sbomify.com/CVE-2026-131296/index.md","name":"CVE-2026-131296","record":{"aliases":["GHSA-9qp5-3v34-h3wr"],"analysis":null,"analysis_generated_by":null,"assigner":"cisco","component":null,"cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a different playbook run log and cause that run to fail, including runs outside the labels that the user could access.\nThe vulnerability is possible because Splunk SOAR does not verify that playbook API requests use the trusted runtime context for the current playbook run.","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":"Improper Access Control through Playbooks in Splunk SOAR","id":"CVE-2026-131296","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":"Single Sign-On Authentication Bypass in Splunk SOAR","id":"CVE-2026-131297"},"nickname":null,"packages":[],"prev":{"headline":"Improper Authorization in Playbook Execution in Splunk SOAR","id":"CVE-2026-131295"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["Splunk"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-131296/"}