CVE-2025-53536: Roo Code allows Potential Remote Code Execution via .vscode/settings.json

Published Jul 7, 2025
·
Updated

Roo Code is an AI-powered autonomous coding agent. Prior to 3.22.6, if the victim had "Write" auto-approved, an attacker with the ability to submit prompts to the agent could write to VS Code settings files and trigger code execution. There were multiple ways to achieve that. One example is with the php.validate.executablePath setting which lets you set the path for the php executable for syntax validation. The attacker could have written the path to an arbitrary command there and then created a php file to trigger it. This vulnerability is fixed in 3.22.6.

Affected Software

2 affected components
Roo Code Roo Code<3.22.6
RooCode Roo Code<3.22.6

Event History

Jul 7, 2025
CVE Published
via MITRE·05:57 PM
Data Sourced
via MITRE·05:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-53536?

CVE-2025-53536 is considered a high severity vulnerability due to the potential for arbitrary code execution.

2

How do I fix CVE-2025-53536?

To fix CVE-2025-53536, upgrade Roo Code to version 3.22.6 or later, which addresses the vulnerability.

3

Who is affected by CVE-2025-53536?

CVE-2025-53536 affects users of Roo Code versions prior to 3.22.6 who have 'Write' auto-approved permissions.

4

What kind of attack is possible due to CVE-2025-53536?

CVE-2025-53536 allows an attacker to execute arbitrary code by exploiting the ability to write to VS Code settings files.

5

When was CVE-2025-53536 published?

CVE-2025-53536 was published in 2025, highlighting a significant security issue with earlier versions of Roo Code.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203