CVE-2026-81834: RooCodeInc Roo-Code code injection in README File Handler

CVE-2026-81834 · Severity: medium · CVSS 6.3 · Published 2026-08-27

Roo-Code is an AI-powered code analysis tool that automatically processes project README files to understand codebase context. The tool fails to sanitize HTML comments in README files, allowing attackers to inject malicious system instructions that are silently executed with full agent privileges. An attacker can plant a malicious README in an npm package or pull request; when a developer opens the project in Roo-Code, the tool automatically processes the file and executes embedded commands to steal credentials (AWS keys, GitHub tokens, SSH keys) or run arbitrary code without any warning or user confirmation.

Technologies: RooCodeInc Roo Code. Vendors: RooCodeInc.

Quick answers

Is CVE-2026-81834 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-81834 being exploited in the wild.
How severe is CVE-2026-81834?
Medium severity, with a CVSS score of 6.3, published 27 August 2026.
Which products and versions are affected?
RooCodeInc Roo Code up to 3.51.1.
Is there a fix for CVE-2026-81834?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-81834 attacked?
It is attacked over the network.
Am I affected by CVE-2026-81834?
Check whether you run RooCodeInc Roo Code at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a code injection flaw (CWE-94, CWE-77) in the README File Handler component, specifically in the ExecaTerminalProcess function. The root cause is that Roo-Code's ReadFileTool automatically reads and parses README.md files, treating HTML comments as trusted system instructions without validation or sanitization. These malicious instructions are directly incorporated into the agent's system context, and when the agent executes commands via ExecaTerminalProcess with shell:true enabled, arbitrary command chaining becomes possible. The attack requires only that a victim opens a project containing a malicious README file (no authentication required; network reachability is implicit in downloading or accessing the project). An attacker can achieve remote code execution, credential exfiltration, and supply chain compromise. The vendor has stated that Roo-Code is no longer supported and the repository is archived; no patches are available.

Affected products

  • RooCodeInc Roo-Code up to 3.51.1

Timeline

  • 2026-08-27: disclosed: Published on NVD
  • 2026-06-20: other: PoC advisory published on GitHub

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.