Quick answers
- Is CVE-2026-110202 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110202 being exploited in the wild.
- How severe is CVE-2026-110202?
- 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-110202?
- 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-110202 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110202?
- 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 exists in the getCommandDecision() function in src/core/auto-approval/commands.ts, which strips shell redirections using the regex /\d*>&\d*/ before checking commands against an allowlist. The regex incorrectly matches bare >& (redirect stdout/stderr to file) in addition to fd-duplication operators like 2>&1. When a command like >&echo touch /tmp/file is processed, the regex removes only the >& operator, leaving echo touch /tmp/file for allowlist checking. The system sees the echo prefix and auto-approves, but bash parses the original string as redirecting output to a file named "echo" then executing the denied touch command. This requires the "always approve execute" feature to be enabled and relies on indirect prompt injection to craft the malicious command.
Affected products
- Roo Code Inc Roo Code through 3.54.0
Timeline
- 2026-10-13: disclosed