{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110202 exists.","fix":"No fix has been published for CVE-2026-110202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110202 is a high-severity vulnerability in RooCodeInc Roo-Code, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-110202 and fix it if it is affected.\n\nWhat it is: CVE-2026-110202 is a high-severity vulnerability in RooCodeInc Roo-Code, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110202 exists.\n\nAffected product: RooCodeInc Roo-Code. 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-110202/ (Markdown: https://insights.sbomify.com/CVE-2026-110202/index.md)","id":"CVE-2026-110202","markdown":"https://insights.sbomify.com/CVE-2026-110202/index.md","name":"CVE-2026-110202","record":{"aliases":["GHSA-v45q-xfmj-r4wr"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AI coding assistant","requires_auth":"none","summary":"Attackers can bypass command approval restrictions in Roo Code to execute arbitrary shell commands on developer machines via prompt injection.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"roo_code","vendor":"roocode"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"Roo Code through 3.54.0 contains a command approval bypass vulnerability in getCommandDecision() that allows attackers to auto-approve denied shell commands by prefixing them with a bare \u003e\u0026 redirect. Attackers using indirect prompt injection can make the allowlist match a redirect target like echo while the shell runs the denied command on the developer machine.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Roo-Code through 3.54.0 Auto-Approve Bypass via Redirect Operator Stripping","id":"CVE-2026-110202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Roo-Code through 3.54.0 Auto-Approve Bypass via Quote Masking Desynchronization","id":"CVE-2026-110203"},"packages":[],"prev":{"headline":"Langflow OSS is affected by multiple vulnerabilities","id":"CVE-2026-110200"},"products":["Roo-Code"],"published":"2026-10-13","related":[{"cvss_score":9.9,"headline":"Roo Code is vulnerable to command injection via GitHub actions workflow","id":"CVE-2025-58371","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2026-30307","kev_date_added":null,"published":"2026-03-30"},{"cvss_score":8.1,"headline":"Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug","id":"CVE-2025-65946","kev_date_added":null,"published":"2025-11-21"},{"cvss_score":8.1,"headline":"Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference","id":"CVE-2025-58370","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":8.1,"headline":"Roo Code: Potential Remote Code Execution via .code-workspace","id":"CVE-2025-58372","kev_date_added":null,"published":"2025-09-05"},{"cvss_score":8.1,"headline":"Roo Code allows Potential Remote Code Execution via .vscode/settings.json","id":"CVE-2025-53536","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":8.1,"headline":"Roo Code Vulnerable to Potential Remote Code Execution via Model Context Protocol","id":"CVE-2025-53098","kev_date_added":null,"published":"2025-06-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["RooCodeInc"]},"summary":"Attackers can bypass command approval restrictions in Roo Code to execute arbitrary shell commands on developer machines via prompt injection.","url":"https://insights.sbomify.com/CVE-2026-110202/"}