Description

A security flaw has been discovered in RooCodeInc Roo-Code up to 3.51.1. Affected by this vulnerability is the function optimizeQuery of the file src/utils/helpers.ts of the component CodeIndexManager. Performing a manipulation results in code injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may 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": "5.5",
  "pubDate": "2026-08-27T20:18:56.520Z",
  "pubdate": "2026-08-27T20:18:56.520Z",
  "executiveSummary": "A critical code injection vulnerability exists within the CodeIndexManager component of RooCodeInc Roo-Code up to version 3.51.1.\nThe vulnerability resides in the optimizeQuery function within src/utils/helpers.ts, allowing remote attackers to execute arbitrary code.\nThis flaw presents a significant security risk, as the project is archived and lacks active maintainer support, leaving it permanently exposed to exploitation.\nPublicly available exploit code increases the risk of successful weaponization by malicious actors.\nSuccessful exploitation allows for remote code execution, potentially leading to full system compromise, unauthorized data access, and further lateral movement within the host environment.\nBecause the vendor has ceased support and explicitly advises against the use of the software, there is no expectation of an official security patch.",
  "technicalDetails": "The vulnerability is a code injection flaw located in the optimizeQuery function within src/utils/helpers.ts of the CodeIndexManager component.\nThe root cause of this vulnerability involves improper neutralization of input data before it is processed or evaluated within the query optimization logic.\nWhen a specially crafted payload is passed to the optimizeQuery function, the application fails to distinguish between legitimate query parameters and executable code sequences.\nThe exploitation flow begins with the attacker providing a malicious input vector that includes system commands or script syntax designed to escape the intended execution context.\nAs the optimizeQuery function processes this input, it fails to sanitize or validate the data, subsequently passing the attacker-controlled input to a sink capable of executing code, such as an evaluation engine or a shell execution primitive.\nThis allows the attacker to achieve remote code execution (RCE) on the underlying host system with the privileges of the application process.\nThe attack is remotely exploitable, requiring no prior authentication or specific user interaction beyond the submission of the malicious input to the susceptible component.\nPost-exploitation impact is severe, enabling the attacker to perform unauthorized operations, manipulate data, exfiltrate sensitive environment variables, or establish persistence on the infected system.\nGiven that the Roo-Code repository is archived, the lack of sanitization controls at the point of ingestion remains unresolved, and the inherent trust placed in the input parameters to optimizeQuery serves as the primary attack vector.\nTechnical analysis suggests that the vulnerability facilitates command injection or expression injection, depending on the specific underlying runtime environment (e.g., Node.js execution context), allowing the attacker to break out of the application's intended operational boundaries."
}