Description

A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-27T20:18:56.720Z",
  "pubdate": "2026-08-27T20:18:56.720Z",
  "executiveSummary": "A critical code injection vulnerability exists within the README File Handler component of RooCodeInc Roo-Code versions up to 3.51.1.\nThe vulnerability originates in the ExecaTerminalProcess function, which improperly handles input, enabling remote attackers to execute arbitrary system commands.\nThis flaw represents a significant security risk, as public exploit code is available, facilitating unauthorized code execution.\nThe affected product is officially end-of-life and unsupported, meaning no security patches or updates will be provided by the vendor to address this flaw.\nSuccessful exploitation allows an attacker to achieve remote code execution (RCE) on the host machine running the affected software.\nThe vulnerability is considered high risk due to the potential for full system compromise, data exfiltration, or persistence mechanisms installation, compounded by the absence of a vendor-supplied remediation path.",
  "technicalDetails": "The vulnerability resides in the ExecaTerminalProcess function, a component responsible for managing and executing terminal processes initiated via the README File Handler.\nThe root cause is an improper sanitization and validation mechanism of input processed by this function, which allows an attacker to inject arbitrary commands into the underlying system shell or execution environment.\nBy manipulating the inputs processed by the README File Handler, an attacker can influence the arguments passed to the system shell. Because the process is invoked using functionality prone to shell injection—or failing to properly escape parameters—the injected payload is executed with the privileges of the Roo-Code application.\nThe exploitation flow typically begins with an attacker delivering a crafted input, likely embedded within a README file or a similarly processed document, that the Roo-Code extension interprets and passes to the ExecaTerminalProcess function.\nUpon triggering this function, the unsanitized input is interpreted as part of a shell command rather than data. This allows the redirection of process execution, the chaining of malicious commands via operators (such as &&, ||, or ;), or the injection of flags that alter the command's behavior.\nThe attack is executable remotely, assuming the attacker can deliver the malicious file or payload that the target system processes using the vulnerable component. No specific authentication is required if the system processes the tainted input automatically or through user interaction with a malicious file.\nPost-exploitation impact is severe, as the attacker achieves remote code execution in the context of the user running the IDE or application. This can lead to unauthorized access to sensitive files, environment variables (including API keys or credentials), and network lateral movement within the host machine's environment.\nAs the vendor has explicitly stated that Roo-Code is an archived, unsupported project, there is no available security update to address the underlying flaw in the ExecaTerminalProcess logic, leaving deployed instances permanently vulnerable."
}