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-65946: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in RooCodeInc Roo-Code

0
High
VulnerabilityCVE-2025-65946cvecve-2025-65946cwe-77cwe-20
Published: Fri Nov 21 2025 (11/21/2025, 22:11:12 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. Prior to version 3.26.7, Due to an error in validation it was possible for Roo to automatically execute commands that did not match the allow list prefixes. This issue has been patched in version 3.26.7.

AI-Powered Analysis

AILast updated: 11/28/2025, 23:33:13 UTC

Technical Analysis

CVE-2025-65946 is a command injection vulnerability classified under CWE-77 and CWE-20 affecting RooCodeInc's Roo-Code, an AI-powered autonomous coding agent integrated into users' code editors. The vulnerability exists in versions prior to 3.26.7 due to improper neutralization of special elements in command inputs, allowing the agent to execute commands that do not conform to the predefined allow list prefixes. This flaw stems from insufficient input validation, enabling attackers to craft malicious commands that the agent executes automatically. Exploitation requires no authentication or user interaction and can be performed remotely over the network, as indicated by the CVSS vector (AV:N/AC:H/PR:N/UI:N). The impact includes full compromise of confidentiality, integrity, and availability of the host system running the vulnerable agent, as arbitrary commands can be executed with the privileges of the user running Roo-Code. Although no known exploits have been reported in the wild, the vulnerability poses a significant risk due to the agent’s integration in development environments where sensitive code and credentials may reside. The issue was addressed in version 3.26.7 by correcting the validation logic to enforce strict adherence to the allow list, preventing unauthorized command execution. Organizations using Roo-Code should prioritize upgrading to the patched version and review their development environment security posture to mitigate potential exploitation.

Potential Impact

For European organizations, this vulnerability presents a critical risk to software development environments where Roo-Code is deployed. Exploitation could lead to unauthorized command execution, resulting in data breaches, codebase tampering, or disruption of development workflows. The compromise of development tools can cascade into supply chain risks, potentially affecting production systems if malicious code is introduced. Confidentiality of proprietary source code and intellectual property is at risk, as well as integrity of software builds. Availability may also be impacted if attackers execute destructive commands. Given the network-exploitable nature without authentication, attackers can target vulnerable systems remotely, increasing the attack surface. Organizations in sectors with high reliance on software development, such as finance, automotive, telecommunications, and technology, are particularly vulnerable. The lack of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score underscores the urgency of patching.

Mitigation Recommendations

1. Immediately upgrade all Roo-Code installations to version 3.26.7 or later to apply the official patch addressing the command injection flaw. 2. Implement network segmentation and firewall rules to restrict access to development environments running Roo-Code, limiting exposure to untrusted networks. 3. Enforce the principle of least privilege by running Roo-Code under user accounts with minimal permissions to reduce potential impact of command execution. 4. Monitor logs and behavior of Roo-Code agents for unusual command executions or anomalies indicative of exploitation attempts. 5. Conduct security awareness training for developers to recognize suspicious activity related to their coding tools. 6. Review and harden the configuration of integrated development environments (IDEs) and associated plugins to minimize attack vectors. 7. Establish incident response procedures specific to development environment compromises to enable rapid containment and recovery. 8. Regularly audit software supply chain components and dependencies to detect unauthorized modifications stemming from compromised development tools.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-18T16:14:56.691Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6920e83b27835fd566e79355

Added to database: 11/21/2025, 10:31:23 PM

Last enriched: 11/28/2025, 11:33:13 PM

Last updated: 1/7/2026, 4:20:43 AM

Views: 206

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats