CVE-2026-110203 — Roo-Code through 3.54.0 Auto-Approve Bypass via Quote Masking Desynchronization
Roo Code through 3.54.0 contains a command approval bypass vulnerability that allows attackers to auto-approve denied shell commands by abusing quote-masking regex in parseCommandLine(). Attackers can use indirect prompt injection with escaped or single-quoted double quotes to hide command separators behind allowlisted prefixes like echo, executing commands without user approval.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Roocode Roo Code, RooCodeInc Roo-Code).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the documented mitigations until a definitive fix is available.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Roocode | Roo Code | ≤ 3.54.0 | Vulnerable | NIST National Vulnerability Database |
| RooCodeInc | Roo-Code | ≤ 3.54.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.7 | CVSS 4.0 | High | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 7.7 | CVSS 4.0 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 14, 2026 → Oct 15, 2026 · 2 reading(s) · max 0.43%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · roocode/roo code
- Source status changed · Undergoing Analysis → Analyzed
- Source status changed · Awaiting Analysis → Undergoing Analysis
- SSVC assessment updated
- Affected products added · roocodeinc/roo-code
- Record published
- CVSS changed · 8.8
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- github.com/7rah/oss-cve/blob/6adb836d24ca446fd168c3acdc4c170beb77fe0f/roocode-qu
- github.com/advisories/GHSA-c42p-7mq6-q83w
- www.vulncheck.com/advisories/roo-code-through-3.54.0-auto-approve-bypass-via-quote-mask
- github.com/RooCodeInc/Roo-Code/blob/v3.54.0/src/shared/parse-command.ts
- nvd.nist.gov/vuln/detail/CVE-2026-110203
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-110205 Roo-Code through 3.54.0 Auto-Approve Bypass via Glob Token Discarding Command Substitution 2d
- High CVE-2026-110206 Roo-Code through 3.54.0 Auto-Approve Bypass via Command Substitution at Command Position 2d
- High CVE-2026-110202 Roo-Code through 3.54.0 Auto-Approve Bypass via Redirect Operator Stripping 2d
- High CVE-2026-110204 Roo-Code through 3.54.0 Auto-Approve Bypass via Funsub Command Substitution 2d
- High CVE-2026-63108 Roo Code 3.54.0 Command Injection via Parameter Expansion Parsing Jul 20, 2026
- Critical CVE-2026-30307 Code Injection in Roocode Roo Code Mar 30, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-110203 is "Roo-Code through 3.54.0 Auto-Approve Bypass via Quote Masking Desynchronization", rated High. It affects Roo Code (Roocode); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.