CVE-2026-81834 in Roo-Code
Summary
by MITRE • 08/27/2026
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.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 08/27/2026
The identified security weakness resides within the ExecaTerminalProcess function of the README File Handler component in RooCodeInc Roo-Code versions up to 3.51.1. This specific architectural flaw allows for code injection attacks, representing a critical failure in input validation and sanitization mechanisms. The vulnerability is classified under CWE-94 as Improper Control of Generation of Code or Command, commonly referred to as code injection. When the application processes user-supplied data through this function without adequate restriction on special characters or command separators, an attacker can inject arbitrary commands that are subsequently executed by the underlying system shell. This type of flaw is particularly dangerous because it bypasses standard application-level security controls and grants the attacker direct access to execute operating system level instructions with the privileges of the running process.
The operational impact of this vulnerability is severe due to its remote exploitability. An adversary can initiate an attack from a distant location without requiring prior authentication or physical access to the target environment, provided that they have control over the input data processed by the README File Handler. The availability of public exploits significantly lowers the barrier for entry, enabling less sophisticated threat actors to leverage this flaw in automated attacks against vulnerable instances. Successful exploitation could lead to full system compromise, allowing attackers to install malware, exfiltrate sensitive data, or use the compromised host as a pivot point for further network intrusion. This aligns with MITRE ATT&CK techniques related to Command and Scripting Interpreter abuse, where adversaries leverage native tools to execute malicious commands within the target environment.
Despite the technical severity of this flaw, it is crucial to contextualize its risk profile based on the current status of the software project. The vendor has explicitly stated that Roo Code is no longer supported, with the repository archived and a clear discouragement against continued usage by users or developers. This lack of active maintenance means there are no forthcoming patches, security updates, or community-driven mitigations to address this vulnerability in future releases. Consequently, any organization or individual still relying on versions up to 3.51.1 is operating with known, unpatched critical vulnerabilities that have been publicly disclosed and exploited. The responsibility for risk management falls entirely on the user to either migrate away from this deprecated software immediately or implement robust compensating controls if migration is not instantly feasible.
To mitigate the risks associated with this vulnerability in environments where legacy systems must remain operational temporarily, strict network segmentation should be enforced to limit exposure to untrusted networks. Input validation at the gateway level using Web Application Firewalls can help filter out malicious payloads attempting to exploit command injection patterns before they reach the application layer. Additionally, running any remaining instances of Roo-Code with minimal privileges ensures that even if code injection occurs, the potential damage is contained within a restricted user context rather than granting administrative control over the host system. However, these measures are temporary band-aids; the definitive and only recommended remediation strategy is to decommission the affected software entirely and transition to actively maintained alternatives that adhere to modern security development lifecycles and receive regular vulnerability assessments.