Roo Code
Roo Code · Extension · homepage · RooCodeInc/Roo-Code
3.54.0latest (2026-05-15)
3.26.7minimum safe version
16advisories for Roo Code
Minimum safe version is set by CVE-2025-65946 (Potential Remote Code Execution via zsh command validation bug, fixed in 3.26.7): the highest fix among Roo Code's medium-or-higher advisories. Only advisories for Roo Code itself are counted. 6 medium-or-higher advisories list no fixed version: check the vendor's guidance before relying on the minimum.
Advisories
| ID | Title | Severity | Fixed in | Published |
|---|---|---|---|---|
| CVE-2026-110206 | Roo Code through 3.54.0 contains a command approval bypass vulnerability in parseCommandLine() that allows attackers to auto-approve arbitra… | High | — | 2026-10-13 |
| CVE-2026-110205 | Roo Code through 3.54.0 contains a command approval bypass vulnerability in parseCommandLine() that discards command substitutions placed ne… | High | — | 2026-10-13 |
| CVE-2026-110204 | Roo Code through 3.54.0 contains a command approval bypass vulnerability that allows attackers to run denied shell commands because parseCom… | High | — | 2026-10-13 |
| CVE-2026-110203 | Roo Code through 3.54.0 contains a command approval bypass vulnerability that allows attackers to auto-approve denied shell commands by abus… | High | — | 2026-10-13 |
| CVE-2026-110202 | Roo Code through 3.54.0 contains a command approval bypass vulnerability in getCommandDecision() that allows attackers to auto-approve denie… | High | — | 2026-10-13 |
| CVE-2025-65946 | Potential Remote Code Execution via zsh command validation bug · sets minimum safe version | High | 3.26.7 | 2025-11-21 |
| CVE-2025-58371 | Critical command injection vulnerability in GitHub actions workflow | Critical | — | 2025-09-04 |
| CVE-2025-58370 | Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference | High | 3.26.0 | 2025-09-04 |
| CVE-2025-58374 | Auto-approve allows npm install execution of malicious postinstall acripts | High | 3.26.0 | 2025-09-04 |
| CVE-2025-58373 | Symlink-bypass of .rooignore leading to unintended file disclosure | Medium | 3.26.0 | 2025-09-04 |
Show 6 older advisories
| ID | Title | Severity | Fixed in | Published |
|---|---|---|---|---|
| CVE-2025-58372 | Potential Remote Code Execution via .code-workspace | High | 3.26.0 | 2025-09-04 |
| CVE-2025-57771 | Potential Remote Code Execution via Auto-Execute Commands | High | 3.25.5 | 2025-08-22 |
| CVE-2025-54377 | Missing Line Break Validation in Command Execution Tool | High | 3.23.19 | 2025-07-23 |
| CVE-2025-53536 | Potential Remote Code Execution via .vscode/settings.json in the Roo Code extension | High | 3.22.6 | 2025-07-07 |
| CVE-2025-53098 | Potential Remote Code Execution via Model Context Protocol in the Roo Code extension | High | 3.20.3 | 2025-06-27 |
| CVE-2025-53097 | Potential Information Leakage via JSON Schema in the Roo Code extension | Medium | 3.20.3 | 2025-06-27 |
Hardening checklist
- Keep auto-update enabled and verify the installed version against the minimum safe version.
- Do not open untrusted repositories with agent mode or auto-approve enabled.
- Restrict MCP servers to an allowlist; review each server's permissions and publisher.
- Never place secrets in project files the agent can read; use a secrets manager or env injection.
Rolling these tools out? See the playbook Secure AI coding tools in your organisation.
Lock it down: AI hardening kit (managed settings and MCP allowlist generators, free, in your browser).
Check your version
Via the public API:
curl -s "https://threatdeck.net/api/v1/tools/roo-code/check?version=<your-version>" Or ask your agent through the ThreatDeck MCP server (https://threatdeck.net/mcp):
check_ai_tool_version { "slug": "roo-code", "version": "<your-version>" } Updated 2026-11-22