dbcve.org
Roo CodeApplication · Roocode

CVE-2025-58372

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-05
Fix available
A fix is available. Upgrade to 3.26.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 is an AI-powered autonomous coding agent that lives in users' editors. Versions 3.25.23 and below contain a vulnerability where certain VS Code workspace configuration files (.code-workspace) are not protected in the same way as the .vscode folder. If the agent was configured to auto-approve file writes, an attacker able to influence prompts (for example via prompt injection) could cause malicious workspace settings or tasks to be written. These tasks could then be executed automatically when the workspace is reopened, resulting in arbitrary code execution. This issue is fixed in version 3.26.0.

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 · high confidence

Roo Code versions 3.25.23 and below fail to apply the same protective controls to .code-workspace files as they do to .vscode folders. When auto-approve file writes is enabled, an attacker with prompt injection capability can cause the agent to write malicious workspace configuration or task definitions to .code-workspace files, which execute automatically upon workspace reopening, achieving arbitrary code execution.

MitigationUpgrade to Roo Code version 3.26.0 or later. Until upgraded, disable the auto-approve file writes configuration setting.

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.26.0

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. Check installed Roo Code version
    Open VS Code or Cursor, access the extensions panel, find Roo Code in the installed extensions list, and note the version number displayed
    Affected if The version is 3.25.23 or below, or any version lower than 3.26.0
  2. Check auto-approve file writes setting
    Open Roo Code settings (Roo Code tab > Settings icon), look for the 'Auto-approve file writes' or 'Auto-approve' configuration option, and note whether it is enabled
    Affected if Auto-approve file writes is enabled (set to true or checked)
  3. Inspect .code-workspace files in project directories
    Search for all .code-workspace files in the user's workspace directories, typically in the root of projects or workspaces; open each file and review the JSON content for unexpected task definitions, extensions, or settings
    Affected if Any .code-workspace file contains suspicious task definitions with shell commands, external extension references, or settings that were not intentionally added by the user

You are affected if your Roo Code version is below 3.26.0 AND auto-approve file writes is enabled, or if you find malicious modifications in any .code-workspace file.

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 3.26.0 or later
Fixed in 3.26.0
Vendor patch github.com →
Interim mitigation

Upgrade to Roo Code version 3.26.0 or later. Until upgraded, disable the auto-approve file writes configuration setting.

Recommended fix High confidence

3.26.0 or later

  1. 1. Open VS Code or your IDE where Roo Code extension is installed
  2. 2. Navigate to the Extensions panel (Ctrl+Shift+X or Cmd+Shift+X)
  3. 3. Search for "Roo Code" or "Roo-Code" in the extensions marketplace
  4. 4. If an update is available, click "Update" to upgrade to version 3.26.0 or later
  5. 5. After updating, restart VS Code to ensure the new version is fully loaded
  6. 6. Verify the installed version is 3.26.0 or higher via Extensions > Installed extensions
Caveat none reported

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

Fix this in Roo Code Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58372 — 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-2025-58372 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