dbcve.org
Roo CodeApplication · Roocode

CVE-2025-58371

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-05
Fix available
A fix is available. Upgrade to 3.26.7 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. In versions 3.26.6 and below, a Github workflow used unsanitized pull request metadata in a privileged context, allowing an attacker to craft malicious input and achieve Remote Code Execution (RCE) on the Actions runner. The workflow runs with broad permissions and access to repository secrets. It is possible for an attacker to execute arbitrary commands on the runner, push or modify code in the repository, access secrets, and create malicious releases or packages, resulting in a complete compromise of the repository and its associated services. This is fixed in version 3.26.7.

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.26.6 and below contain a code injection vulnerability in a GitHub Actions workflow that processes unsanitized pull request metadata in a privileged context. Attackers can craft malicious PR titles, descriptions, or other metadata containing shell commands that execute with the workflow's elevated permissions and access to repository secrets, enabling full repository compromise including arbitrary code execution, secret exfiltration, and unauthorized code pushes.

MitigationUpgrade Roo Code to version 3.26.7 or later. Review GitHub Actions workflow files to ensure all external inputs (especially PR metadata) are properly sanitized before use in privileged contexts, and rotate any repository secrets that may have been exposed.

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

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 Roo Code and navigate to the extensions/settings panel, or check the extension package if installed via package manager. Look for the version number displayed.
    Affected if Version is 3.26.6 or below (any version < 3.26.7)
  2. Confirm GitHub Actions workflow usage
    Identify whether you use the GitHub Actions integration within Roo Code. Check if you have any workflow files (.yml/.yaml in .github/workflows/) that are processed by Roo Code.
    Affected if You actively use the GitHub Actions workflow features in Roo Code with pull request metadata processing

You are affected if you have Roo Code version 3.26.6 or below installed AND use the GitHub Actions workflow integration that processes pull request metadata.

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

Upgrade Roo Code to version 3.26.7 or later. Review GitHub Actions workflow files to ensure all external inputs (especially PR metadata) are properly sanitized before use in privileged contexts, and rotate any repository secrets that may have been exposed.

Recommended fix High confidence

3.26.7

  1. Open VS Code and navigate to the Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
  2. Search for "Roo Code" or "Roo-Code" in the extensions marketplace
  3. Locate the Roo Code extension in the search results
  4. Click on the extension to view its details
  5. If an update is available, click the "Update" button to upgrade to version 3.26.7 or later
  6. Alternatively, click the "Install" button if not already installed, specifying version 3.26.7
  7. After the upgrade completes, restart VS Code to ensure the patched version is fully loaded
  8. Verify the installed version is 3.26.7 or higher by checking the extension details in the Extensions view

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

Fix this in Roo Code Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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