Skip to main content
VulnerabilityPublished Updated

CVE-2025-65946: RooCodeInc Roo-Code · Command Injection

Affects RooCodeInc Roo-CodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 3.26.7 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.26.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade roocodeinc/Roo-Code to 3.26.7.

Affected software

ProductAffectedFixed in
GitHubroocodeinc/Roo-Codepkg:github/roocodeinc/Roo-CodeOther threatsAffected
  • <3.26.7
Fixed in
  • 3.26.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  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.

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.

References

Community reviews

Loading reviews…