Approved changes feed: RSS · Atom
cpe:2.3:a:roocode:roo_code:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Roocode (97dfec9b-cb18-5bea-b9cc-b1bd6387560a) |
|---|---|
| Product | Roo Code (94bd5a1e-dc28-5d5f-84ba-e636957f3d8e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/roocodeinc/roo-code |
purl2cpe | 2026-06-01 10:18:09.323144 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-110206 |
vulnerable | 2026-11-03 10:16:00.359949 |
Roo-Code through 3.54.0 Auto-Approve Bypass via Command Substitution at Command Position
HIGH (8.8)
Roo Code through 3.54.0 contains a command approval bypass vulnerability in parseCommandLine() that allows attackers to auto-approve arbitrary shell commands by placing a command substitution in command position. Attackers using indirect prompt injection can submit commands like $(echo touch /tmp/x) that pass the echo allowlist check, causing the shell to execute the output without user approval.
Published: 2026-10-13T18:49:58.125Z
Updated: 2026-10-16T22:27:58.356Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-30307 |
vulnerable | 2026-06-08 07:57:14.020199 |
Details available
Roo Code's command auto-approval module contains a critical OS command injection vulnerability that renders its whitelist security mechanism completely ineffective. The system relies on fragile regular expressions to parse command structures; while it attempts to intercept dangerous operations, it fails to account for standard Shell command substitution Roo Code (specifically$(...)and backticks ...). An attacker can construct a command such as git log --grep="$(malicious_command)", forcing Syntx to misidentify it as a safe git operation and automatically approve it. The underlying Shell prioritizes the execution of the malicious code injected within the arguments, resulting in Remote Code Execution without any user interaction.
Published: 2026-03-30T00:00:00.000Z
Updated: 2026-04-01T17:52:54.351Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65946 |
vulnerable | 2026-06-08 07:39:21.087947 |
Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug
HIGH (8.1)
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.
Published: 2025-11-21T22:11:12.163Z
Updated: 2025-11-25T18:56:33.525Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58374 |
vulnerable | 2026-06-08 07:35:18.060790 |
Roo Code: Auto-approve allows npm install execution of malicious postinstall scripts
HIGH (7.8)
Roo Code is an AI-powered autonomous coding agent that lives in users' editors. Versions 3.25.23 and below contain a default list of allowed commands that do not need manual approval if auto-approve is enabled, and npm install is included in that list. Because npm install executes lifecycle scripts, if a repository’s package.json file contains a malicious postinstall script, it would be executed automatically without user approval. This means that enabling auto-approved commands and opening a malicious repo could result in arbitrary code execution. This is fixed in version 3.26.0.
Published: 2025-09-06T02:19:40.112Z
Updated: 2025-09-08T14:05:33.807Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58373 |
vulnerable | 2026-06-08 07:35:18.060342 |
Roo Code: Symlink-bypass of .rooignore can lead to unintended file disclosure
MEDIUM (5.5)
Roo Code is an AI-powered autonomous coding agent that lives in users' editors. Versions 3.25.23 and below contain a vulnerability where .rooignore protections could be bypassed using symlinks. This allows an attacker with write access to the workspace to trick the extension into reading files that were intended to be excluded. As a result, sensitive files such as .env or configuration files could be exposed. An attacker able to modify files within the workspace could gain unauthorized access to sensitive information by bypassing .rooignore rules. This could include secrets, configuration details, or other excluded project data. This is fixed in version 3.26.0.
Published: 2025-09-05T22:55:54.546Z
Updated: 2025-09-08T20:12:43.405Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58372 |
vulnerable | 2026-06-08 07:35:18.060070 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58371 |
vulnerable | 2026-06-08 07:35:18.059778 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58370 |
vulnerable | 2026-06-08 07:35:18.059393 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-54377 |
vulnerable | 2026-06-08 07:33:12.506080 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53536 |
vulnerable | 2026-06-08 07:31:14.679492 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53098 |
vulnerable | 2026-06-08 07:31:13.944334 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53097 |
vulnerable | 2026-06-08 07:31:13.943949 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.