Quick answers
- Is CVE-2026-110204 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110204 being exploited in the wild.
- How severe is CVE-2026-110204?
- High severity, with a CVSS score of 8.8, published 13 October 2026.
- Which products and versions are affected?
- Roo Code Inc Roo Code through 3.54.0.
- Is there a fix for CVE-2026-110204?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-110204 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110204?
- Check whether you run Roo Code Inc Roo Code or Roocode Roo Code at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is in parseCommand() in parse-command.ts, which masks shell constructs before checking commands against allowlists. The regex /\$\{[^}]+\}/ intended to mask parameter expansions like ${var:-default} also matches the bash 5.3+ command substitution syntax ${ command; } (funcsub), treating it as an opaque parameter expansion and never examining the command inside. When a denied command is embedded as echo ${ touch /tmp/file; }, the parser approves it because it matches the "echo" allowlist prefix. On bash 5.3+, ksh93, or other shells supporting funsubs, the braces execute the hidden command. The attack requires the auto-approval feature enabled and targets the parseCommand/getCommandDecision logic.
Affected products
- Roo Code Inc Roo Code through 3.54.0
Timeline
- 2026-10-13: disclosed