dbcve.org
Roo CodeApplication · Roocode

CVE-2026-30307

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to after 3.46.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Roo Code's command auto-approval module contains a critical OS command injection vulnerability that renders its whitelist security mechanism completely ineffective. The system relies on fragile regular expressions to parse command structures; while it attempts to intercept dangerous operations, it fails to account for standard Shell command substitution Roo Code (specifically$(...)and backticks ...). An attacker can construct a command such as git log --grep="$(malicious_command)", forcing Syntx to misidentify it as a safe git operation and automatically approve it. The underlying Shell prioritizes the execution of the malicious code injected within the arguments, resulting in Remote Code Execution without any user interaction.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Roo Code's auto-approval module uses flawed regular expression parsing to whitelist commands, but fails to filter shell command substitution syntax ($(...) and backticks). An attacker can inject malicious commands into seemingly safe git operations like 'git log --grep="$(malicious_command)"', bypassing the whitelist and achieving remote code execution.

MitigationImplement strict input validation to escape or reject shell command substitution characters ($( and `) in all command arguments before whitelist evaluation, and treat all user-controlled input as untrusted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Roo CodeApplication
Affected:<= 3.46.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Roo Code installation and version
    Check the installed version of the Roo Code extension in your VS Code or IDE extension manager. Compare against the affected range: versions <= 3.46.1
    Affected if The installed version is 3.46.1 or lower
  2. Locate auto-approval module configuration
    Look for Roo Code settings related to auto-approval, command whitelisting, or security policy configuration in the extension's settings file or IDE preferences
    Affected if Auto-approval or command whitelisting settings are present and enabled in the configuration
  3. Verify shell substitution filtering in command arguments
    Inspect the auto-approval configuration for how it handles command arguments, specifically looking for whether $( and backtick characters are validated or rejected
    Affected if The auto-approval module does not explicitly filter or reject shell command substitution characters ($( and `) from command arguments before whitelist evaluation
  4. Test command injection via grep parameter
    If auto-approval is active, attempt a safe test command such as: git log --grep="$(echo test)" to see if the substitution is executed or blocked
    Affected if The command executes and the shell substitution $(echo test) is evaluated rather than being treated as a literal string
  5. Review trusted command whitelist entries
    Examine the whitelist of approved commands in the auto-approval module settings to see if git commands with variable arguments are included
    Affected if Git commands or other commands that accept user-controlled arguments are whitelisted without proper input sanitization

You are affected if you have Roo Code version 3.46.1 or lower with the auto-approval module enabled and the whitelist allows commands without filtering shell substitution characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.46.1
Interim mitigation

Implement strict input validation to escape or reject shell command substitution characters ($( and `) in all command arguments before whitelist evaluation, and treat all user-controlled input as untrusted.

Recommended fix High confidence

Roo Code version > 3.46.1

  1. 1. Check the currently installed Roo Code version in VS Code extensions
  2. 2. Visit the Roo Code VS Code marketplace page or GitHub releases page to identify the latest available version
  3. 3. Upgrade Roo Code to a version higher than 3.46.1 (the fixed release that addresses this command injection vulnerability)
  4. 4. After upgrading, verify the extension is functioning correctly
  5. 5. Test that the command auto-approval module properly rejects commands with shell substitution syntax ($(...) or backticks)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Roo Code Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data