# CVE-2026-63108: Roo Code 3.54.0 Command Injection via Parameter Expansion Parsing

> Attackers can execute arbitrary commands by bypassing allowlist checks in Roo Code's auto-approve feature via nested parameter expansions.

- **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:** 20 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-5xxh-cfjg-qm65

## What is CVE-2026-63108?

CVE-2026-63108 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 20 Jul 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 a command injection vulnerability in the auto-approve execute feature that allows attackers to bypass allowlist/denylist enforcement by nesting command substitutions inside parameter expansion defaults. The command parser in parse-command.ts replaces parameter expansions with opaque placeholders before extracting command substitutions, causing the containsDangerousSubstitution guard to miss nested payloads, which are then auto-approved based on the outer allowlisted command prefix and executed by the shell via execa, enabling arbitrary command execution.

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

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


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

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

## Is CVE-2026-63108 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63108 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63108 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 20 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63108 exists.

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-63108/ (Markdown: https://insights.sbomify.com/CVE-2026-63108/index.md)
```

## Sources

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

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