Quick answers
- Is CVE-2026-82536 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82536 being exploited in the wild.
- How severe is CVE-2026-82536?
- High severity, with a CVSS score of 8.8, published 8 September 2026.
- Which products and versions are affected?
- Roo Code Roo-Code through 3.54.0.
- Is there a fix for CVE-2026-82536?
- 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-82536 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82536?
- Check whether anything you run is named in the advisory. 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
This is an incomplete input validation vulnerability (CWE-184) in the command parser's operator tokenization logic. The parseCommand function in src/shared/parse-command.ts splits shell commands into sub-commands by recognizing specific operator tokens (&&, ||, ;, |, &), then validates each sub-command against an allowlist and denylist. However, the |& operator (bash's stderr-to-stdout redirect pipe) is not included in the split list, causing it to be folded into the preceding sub-command rather than starting a new one. An attacker can chain an allowlisted command (e.g., "echo") with |& followed by a denied command (e.g., "touch"), resulting in a single token that matches the allowlist and is auto-approved. Bash then executes the full pipeline, running the denied command with the agent's privileges. Exploitation requires the "always approve execute" feature to be enabled and attacker control over proposed commands. A patch adding |& to the operator token list is required to fix the bypass.
Affected products
- Roo Code Roo-Code through 3.54.0
Timeline
- 2026-09-08: disclosed