{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131269 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-131269 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131269 is a high-severity code injection vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-131269 and fix it if it is affected.\n\nWhat it is: CVE-2026-131269 is a high-severity code injection vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-131269 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\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-131269/ (Markdown: https://insights.sbomify.com/CVE-2026-131269/index.md)","id":"CVE-2026-131269","markdown":"https://insights.sbomify.com/CVE-2026-131269/index.md","name":"CVE-2026-131269","record":{"aliases":["GHSA-89q9-g5hr-32f8"],"analysis":{"component_type":"web_application","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"security orchestration platform","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Users with Apps edit permission can make Splunk SOAR execute arbitrary code on the host when validating an installed app.","user_interaction":"not_required","vuln_class":"code_injection","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could cause Splunk SOAR to execute arbitrary code on the host when the user validates an installed app.\nThe vulnerability is possible because the app validation workflow does not isolate untrusted code from the trusted environment.","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 Python Dependencies in Splunk SOAR","id":"CVE-2026-131269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Path Traversal through the REST API in Splunk SOAR","id":"CVE-2026-131270"},"nickname":null,"packages":[],"prev":{"headline":"Remote Code Execution (RCE) through the REST API in Splunk SOAR","id":"CVE-2026-131268"},"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":"Users with Apps edit permission can make Splunk SOAR execute arbitrary code on the host when validating an installed app.","url":"https://insights.sbomify.com/CVE-2026-131269/"}