CVE-2026-81834

Deferred Deferred - Pending Action

Code Injection in Roo-Code via README File Handler

Publication date: 2026-08-27

Last updated on: 2026-08-28

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-08-28

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-81834

Affected Vendors & Products

Vendor	Product	Version / Range
roocodeinc	roo-code	to 3.51.1 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-74	The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-94	The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

Executive Summary

This vulnerability is a code injection flaw in RooCodeInc Roo-Code up to version 3.51.1. It occurs in the ExecaTerminalProcess function of the README File Handler component. Attackers can exploit it by embedding malicious commands in HTML comments within README files, which are then executed when users interact with the agent. The issue stems from a lack of validation or sanitization of README content, allowing remote code execution and potential credential theft.

Detection Guidance

Since Roo-Code is no longer supported, detection involves checking for suspicious README files or network activity. Look for unexpected outbound connections from Roo-Code processes and inspect README.md files for hidden HTML comments containing commands. Use tools like grep to search for patterns like  in README files across your projects.

Impact Analysis

This vulnerability allows attackers to execute arbitrary code remotely on your system when you open a project in Roo-Code. It can lead to credential exfiltration, such as stealing AWS, GitHub, or SSH keys, and sensitive data being sent to attacker-controlled servers. The attack is silent with no warnings displayed, making it difficult to detect.

Compliance Impact

This vulnerability could lead to data breaches, exposing personal or sensitive data, which may violate GDPR and HIPAA compliance requirements. Organizations using Roo-Code may face legal and regulatory penalties due to unauthorized data access or exfiltration resulting from this flaw.

Mitigation Strategies

Stop using Roo-Code immediately as it is no longer supported. Remove the application from your system. Review and sanitize all README files in your projects to remove any hidden HTML comments. Implement stricter input validation and user approval mechanisms for any similar tools you use.

Hi! I’m here to help you understand CVE-2026-81834. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70