{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-58370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58370 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-58370 and fix it if it is affected.\n\nWhat it is: CVE-2025-58370 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-58370 in the wild and no public exploit code.\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-2025-58370/ (Markdown: https://insights.sbomify.com/CVE-2025-58370/index.md)","id":"CVE-2025-58370","markdown":"https://insights.sbomify.com/CVE-2025-58370/index.md","name":"CVE-2025-58370","record":{"aliases":["GHSA-2rm5-cvcm-7592"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"AI coding agent","requires_auth":"none","summary":"Attackers can execute arbitrary commands if auto-approval is enabled, requiring an upgrade to the AI coding agent.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"roo_code","vendor":"roocode"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Roo Code is an AI-powered autonomous coding agent that lives in users' editors. Versions below 3.26.0 contain a vulnerability in the command parsing logic where the Bash parameter expansion and indirect reference were not handled correctly. If the agent was configured to auto-approve execution of certain commands, an attacker able to influence prompts could abuse this weakness to execute additional arbitrary commands alongside the intended one. This is fixed in version 3.26.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference","id":"CVE-2025-58370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Roo Code is vulnerable to command injection via GitHub actions workflow","id":"CVE-2025-58371"},"packages":[],"prev":{"headline":"fs2: Half-shutdown of socket during TLS handshake may result in spin loop on opposite side","id":"CVE-2025-58369"},"products":["Roo-Code"],"published":"2025-09-05","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 .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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-08","vendors":["RooCodeInc"]},"summary":"Attackers can execute arbitrary commands if auto-approval is enabled, requiring an upgrade to the AI coding agent.","url":"https://insights.sbomify.com/CVE-2025-58370/"}