Skip to content
Connect AISign inSign up free
CVE-2025-530988.1HighCWE-77

CVE-2025-53098: Roo Code Vulnerable to Potential Remote Code Execution via Model Context Protocol

RooCodeInc · Roo-Code

Affected: RooCodeInc Roo-Code · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.7%probability of exploitation in the next 30 days
52nd percentile
050100

Higher than 52% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

Roo Code is an AI-powered autonomous coding agent. The project-specific MCP configuration for the Roo Code agent is stored in the `.roo/mcp.json` file within the VS Code workspace. Because the MCP configuration format allows for execution of arbitrary commands, prior to version 3.20.3, it would have been possible for an attacker with access to craft a prompt to ask the agent to write a malicious command to the MCP configuration file. If the user had opted-in to auto-approving file writes within the project, this would have led to arbitrary command execution. This issue is of moderate severity, since it requires the attacker to already be able to submit prompts to the agent (for instance through a prompt injection attack), for the user to have MCP enabled (on by default), and for the user to have enabled auto-approved file writes (off by default). Version 3.20.3 fixes the issue by adding an additional layer of opt-in configuration for auto-approving writing to Roo's configuration files, including all files within the `.roo/` folder.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • RooCodeInc · Roo-Code< 3.20.3

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
June 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-53098 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References