Quick answers
- Is CVE-2026-110203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110203 being exploited in the wild.
- How severe is CVE-2026-110203?
- High severity, with a CVSS score of 8.8, published 13 October 2026.
- Which products and versions are affected?
- Roo Code through 3.54.0.
- Is there a fix for CVE-2026-110203?
- 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-110203 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110203?
- Check whether you run 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 lies in the parseCommand function's regex-based quote masking, which uses /"[^"]*"/ to remove quoted strings before command parsing. This regex does not implement bash quoting semantics: it fails to recognize escaped quotes (\"), single quotes, and ANSI-C quotes ($'…') as bash does. An attacker can use commands like echo \";touch /tmp/pwned;\" where bash treats the backslash-escaped quotes as literal characters (allowing the semicolon separator to execute), but the regex incorrectly pairs them and hides the separator in a placeholder, causing the full command to be treated as a single echo sub-command that matches the allowlist. The flaw allows arbitrary command injection when auto-approval is enabled.
Affected products
- Roo Code through 3.54.0
Timeline
- 2026-10-13: disclosed