Secure Autonomous
FeedbackGet alertsCheck a deployment
Signals › SIG-2026-10-14-001

CVE-2026-110202 to 110206: Roo Code

Five National Vulnerability Database (NVD) records say that in Roo Code through 3.54.0 crafted shell commands delivered by indirect prompt injection can pass the auto-approval command allowlist and run without user approval (one record only on bash 5.3+ or ksh93); no fixed version is named.

VulnerabilitySoftware agents · Enterprise work agentsRecord published 2026-10-13Posted 2026-10-14
SIG-2026-10-14-001National Vulnerability Database record ↗

The record

Kind
Vulnerability
Source record
CVE-2026-110202: Roo Code through 3.54.0 contains a command approval bypass vulnerability in getCommandDecision() that allows a (National Vulnerability Database record)
Record published
2026-10-13
Posted here
2026-10-14
World
Software agents · Enterprise work agents
Controls concerned
Pre-execution validation C-D1; Retrieved content as data C-I1
Checked
Checked against its record on 2026-10-22 by a reader who did not draft it; report verification/reports/SIG-2026-10-14-001-2026-10-22.md.

A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.

Corrections

Changes to what this signal says, with the reason. Every earlier version is kept.

What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.

New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.

Get the weekly email

Newer: New York City Council: SpaceXAI agrees to testify on artificial intelligence safety following a subpoena
Older: CVE-2026-77366: obsidian-tc

Is this wrong? Dispute it with the record that shows otherwise. All signals · RSS feed.

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?