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

> Attackers can achieve remote code execution by tricking the AI agent into writing malicious commands to its configuration file if auto-approval is enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2025
- **Updated:** 3 Jul 2025
- **Also known as:** GHSA-5x8h-m52g-5v54

## What is CVE-2025-53098?

CVE-2025-53098 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 27 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-53098?

It affects 1 product.


Products: Roocode Roo Code.

## How do I fix CVE-2025-53098?

No fix has been published for CVE-2025-53098 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53098 being exploited?

There is no known exploitation of CVE-2025-53098 in the wild and no public exploit code.

## Other vulnerabilities in RooCodeInc Roo-Code

- [CVE-2025-58371](https://insights.sbomify.com/CVE-2025-58371/): Roo Code is vulnerable to command injection via GitHub actions workflow (critical 9.9)
- [CVE-2026-30307](https://insights.sbomify.com/CVE-2026-30307/): Command injection in n/a (critical 9.8)
- [CVE-2025-65946](https://insights.sbomify.com/CVE-2025-65946/): Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug (high 8.1)
- [CVE-2025-58370](https://insights.sbomify.com/CVE-2025-58370/): Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference (high 8.1)
- [CVE-2025-58372](https://insights.sbomify.com/CVE-2025-58372/): Roo Code: Potential Remote Code Execution via .code-workspace (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53098 and fix it if it is affected.

What it is: CVE-2025-53098 is a high-severity command injection vulnerability in RooCodeInc Roo-Code, published on 27 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53098 in the wild and no public exploit code.

Affected product: RooCodeInc Roo-Code. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53098/ (Markdown: https://insights.sbomify.com/CVE-2025-53098/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53098
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53098
- OSV: https://osv.dev/vulnerability/CVE-2025-53098

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53098/
Summaries are generated and may contain mistakes; the official description above is the record.