# CVE-2026-82536: Roo-Code 3.54.0 Auto-Approve Bypass via Shell Command Pipe Operator

> Attackers bypass auto-approval restrictions in Roo-Code to execute arbitrary shell commands with developer privileges via pipe operator injection.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-cvxc-67pr-wffj

## What is CVE-2026-82536?

CVE-2026-82536 is a high-severity vulnerability in RooCodeInc Roo-Code, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Roo-Code through 3.54.0 contains an auto-approve bypass vulnerability in the shell command parsing logic that allows attackers to execute denied shell commands by exploiting the omission of the bash pipe operator from the command parser's operator token set. Attackers can craft a command line with an allowlisted prefix followed by the stderr-redirecting pipe operator and a denied command, causing the parser to approve the full pipeline while bash executes the denied component with the agent's auto-execute privileges on the developer's machine.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-82536?


## How do I fix CVE-2026-82536?

No fix has been published for CVE-2026-82536 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82536 being exploited?

There is no known exploitation of CVE-2026-82536 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82536 and fix it if it is affected.

What it is: CVE-2026-82536 is a high-severity vulnerability in RooCodeInc Roo-Code, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82536 in the wild and no public exploit code.

Affected product: RooCodeInc Roo-Code. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82536/ (Markdown: https://insights.sbomify.com/CVE-2026-82536/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82536
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82536
- OSV: https://osv.dev/vulnerability/CVE-2026-82536

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82536/
Summaries are generated and may contain mistakes; the official description above is the record.