CVE-2025-58371: Roo Code is vulnerable to command injection via GitHub actions workflow
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Roo Codeto a version that resolves this vulnerability.Fixed in 3.26.7
Event History
Frequently Asked Questions
What is the severity of CVE-2025-58371?
CVE-2025-58371 is rated as critical due to its potential for Remote Code Execution (RCE).
How do I fix CVE-2025-58371?
To fix CVE-2025-58371, update Roo Code to version 3.26.7 or later as it addresses the vulnerability.
What are the impacts of CVE-2025-58371?
CVE-2025-58371 allows attackers to execute arbitrary code remotely, compromising system integrity and security.
Which versions of Roo Code are affected by CVE-2025-58371?
Roo Code versions 3.26.6 and below are vulnerable to CVE-2025-58371.
Is there a workaround for CVE-2025-58371 if I cannot update?
Disabling automated GitHub workflows may serve as a temporary workaround for CVE-2025-58371 until you can update.