Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-58370: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in RooCodeInc Roo-Code

0
High
VulnerabilityCVE-2025-58370cvecve-2025-58370cwe-78
Published: Fri Sep 05 2025 (09/05/2025, 22:09:04 UTC)
Source: CVE Database V5
Vendor/Project: RooCodeInc
Product: Roo-Code

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.

AI-Powered Analysis

AILast updated: 09/12/2025, 23:54:40 UTC

Technical Analysis

CVE-2025-58370 is a high-severity OS command injection vulnerability affecting RooCodeInc's Roo-Code product, specifically versions prior to 3.26.0. Roo-Code is an AI-powered autonomous coding agent integrated within users' code editors to assist with coding tasks. The vulnerability arises from improper handling of Bash parameter expansion and indirect references in the command parsing logic. When the agent is configured to auto-approve execution of certain commands, an attacker who can influence the prompts given to the agent can exploit this flaw to inject and execute arbitrary OS commands alongside the intended commands. This means that an attacker could escalate their control beyond the expected command scope, potentially executing malicious commands on the host system without requiring user interaction or authentication. The vulnerability is classified under CWE-78, indicating improper neutralization of special elements used in OS commands. The CVSS v3.1 base score is 8.1, reflecting a high severity due to the network attack vector, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the flaw represents a significant risk, especially in environments where Roo-Code is used with auto-approval enabled. The issue is resolved in version 3.26.0 of Roo-Code, and users are strongly advised to upgrade to this or later versions to mitigate the risk.

Potential Impact

For European organizations, this vulnerability poses a substantial risk, particularly for software development teams and enterprises relying on Roo-Code for coding automation. Successful exploitation could lead to unauthorized command execution on developers' machines or build servers, potentially compromising sensitive source code, intellectual property, and internal infrastructure. The breach of confidentiality could expose proprietary code or credentials, while integrity and availability impacts could disrupt development pipelines or introduce malicious code into production environments. Given the autonomous nature of the agent and the lack of required user interaction or privileges, attackers could leverage this vulnerability to establish persistent footholds or pivot within corporate networks. Organizations in sectors with high reliance on software development, such as finance, telecommunications, and critical infrastructure, may face increased risks of espionage, sabotage, or data leakage. Furthermore, the vulnerability could be exploited as an initial access vector in broader cyberattack campaigns targeting European enterprises.

Mitigation Recommendations

To mitigate this vulnerability effectively, European organizations should: 1) Immediately upgrade all Roo-Code instances to version 3.26.0 or later, where the command parsing flaw is fixed. 2) Review and disable any auto-approval settings for command execution within Roo-Code to reduce the risk of automated exploitation. 3) Implement strict input validation and sanitization on any user-generated prompts or inputs that interact with Roo-Code to prevent injection of malicious commands. 4) Monitor logs and command execution histories for unusual or unexpected commands that could indicate exploitation attempts. 5) Employ endpoint detection and response (EDR) solutions to detect anomalous process executions stemming from Roo-Code. 6) Enforce the principle of least privilege on developer workstations and build servers to limit the impact of any successful command injection. 7) Conduct security awareness training for developers to recognize suspicious behaviors related to autonomous coding agents. 8) Integrate Roo-Code usage monitoring into existing security information and event management (SIEM) systems for real-time alerting. These targeted measures go beyond generic patching and help reduce the attack surface and detect potential exploitation attempts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-29T16:19:59.012Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68bb63db535f4a977319b0e8

Added to database: 9/5/2025, 10:27:39 PM

Last enriched: 9/12/2025, 11:54:40 PM

Last updated: 10/21/2025, 4:35:12 AM

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats