CVE-2025-53098

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

June 27, 2025

Last Modified

September 15, 2025

Advisory Details (2)

Auto-updated Sep 9, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Potential Remote Code Execution via Model Context Protocol in the Roo Code extension · Advisory · RooCodeInc/Roo-Code · GitHub

https://github.com/RooCodeInc/Roo-Code/security/advisories/GHSA-5x8h-m52g-5v54
github_commit

commit 7d0b22f9e659 (RooCodeInc/Roo-Code)

Fix landed in RooCodeInc/Roo-Code commit 7d0b22f9e659 — awaiting tagged release

https://github.com/RooCodeInc/Roo-Code/commit/7d0b22f9e659dc6c26aab0bacbea27874986e772

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-19 15:42 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-18 19:27 UTCEPSS rescore
  6. 2026-09-17 19:29 UTCEPSS rescore
  7. 2026-09-16 14:07 UTCEPSS rescore
  8. 2026-09-16 05:14 UTCEPSS rescore
  9. 2026-09-13 16:46 UTCEPSS rescore
  10. 2026-09-13 08:54 UTCOSV refresh
  11. 2026-09-12 15:00 UTCEPSS rescore
  12. 2026-09-11 14:52 UTCEPSS rescore
  13. 2026-09-11 09:36 UTCEPSS rescore
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-08 21:59 UTCEPSS rescore
  16. 2026-09-07 16:00 UTCEPSS rescore
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-05 15:28 UTCEPSS rescore
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:11 UTCEPSS rescore
  21. 2026-09-01 13:53 UTCEPSS rescore
  22. 2026-09-01 04:38 UTCEPSS rescore
  23. 2026-08-30 19:16 UTCEPSS rescore
  24. 2026-08-30 01:21 UTCEPSS rescore
  25. 2026-08-28 21:40 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:24 UTCEPSS rescore
  2. 2026-08-26 14:45 UTCEPSS rescore
  3. 2026-08-25 13:48 UTCEPSS rescore
  4. 2026-08-25 09:41 UTCOSV refresh
  5. 2026-08-24 14:16 UTCEPSS rescore
  6. 2026-08-24 09:22 UTCEPSS rescore
  7. 2026-08-23 00:18 UTCEPSS rescore
  8. 2026-08-21 23:48 UTCEPSS rescore
  9. 2026-08-20 22:54 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:47 UTCEPSS rescore
  12. 2026-08-17 13:46 UTCEPSS rescore
  13. 2026-08-16 14:55 UTCEPSS rescore
  14. 2026-08-16 02:13 UTCEPSS rescore
  15. 2026-08-15 01:29 UTCEPSS rescore
  16. 2026-08-13 21:59 UTCEPSS rescore
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-10 23:59 UTCEPSS rescore
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 02:23 UTCOSV refresh
  23. 2026-08-08 16:36 UTCEPSS rescore
  24. 2026-08-07 16:26 UTCEPSS rescore
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-05 19:16 UTCEPSS rescore
  27. 2026-08-04 15:09 UTCEPSS rescore
  28. 2026-08-04 15:09 UTCEPSS rescore
  29. 2026-08-04 10:37 UTCEPSS rescore
  30. 2026-08-03 10:35 UTCEPSS rescore
  31. 2026-08-02 02:26 UTCEPSS rescore
  32. 2026-08-01 04:15 UTCEPSS rescore
  33. 2026-07-30 16:27 UTCEPSS rescore
  34. 2026-07-30 01:30 UTCEPSS rescore
  35. 2026-07-28 15:35 UTCEPSS rescore
  36. 2026-07-26 14:54 UTCEPSS rescore
  37. 2026-07-25 14:17 UTCEPSS rescore
  38. 2026-07-24 14:17 UTCEPSS rescore
  39. 2026-07-24 02:41 UTCOSV refresh
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 02:58 UTCEG score recompute
  42. 2026-07-22 14:08 UTCEPSS rescore
  43. 2026-07-22 14:07 UTCEPSS rescore
  44. 2026-07-21 15:24 UTCEPSS rescore
  45. 2026-07-20 17:08 UTCEPSS rescore
  46. 2026-07-19 14:30 UTCEPSS rescore
  47. 2026-07-19 14:30 UTCEPSS rescore
  48. 2026-07-19 02:28 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-16 17:02 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 01:59 UTCEPSS rescore
  54. 2026-07-15 01:59 UTCEPSS rescore
  55. 2026-07-13 22:29 UTCEPSS rescore
  56. 2026-07-13 06:12 UTCEPSS rescore
  57. 2026-07-13 06:12 UTCEPSS rescore
  58. 2026-07-12 05:46 UTCEPSS rescore
  59. 2026-07-11 08:27 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-09 19:09 UTCEPSS rescore
  62. 2026-07-08 15:15 UTCEPSS rescore
  63. 2026-07-07 13:45 UTCEPSS rescore
  64. 2026-07-06 21:04 UTCOSV refresh
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 16:27 UTCEPSS rescore
  67. 2026-07-06 02:23 UTCEPSS rescore
  68. 2026-07-06 02:23 UTCEPSS rescore
  69. 2026-07-05 02:30 UTCEPSS rescore
  70. 2026-07-04 06:30 UTCEPSS rescore
  71. 2026-07-02 17:01 UTCEPSS rescore
  72. 2026-07-01 15:06 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-29 14:06 UTCEPSS rescore
  75. 2026-06-29 14:06 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-53098?
CVE-2025-53098 is a high vulnerability published on June 27, 2025. 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…
When was CVE-2025-53098 disclosed?
CVE-2025-53098 was first published in the National Vulnerability Database on June 27, 2025, with the most recent update on September 15, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-53098 actively exploited?
CVE-2025-53098 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.3% of all scored CVEs.
What is the CVSS score of CVE-2025-53098?
CVE-2025-53098 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-53098?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-53098, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-53098

Explore →

Is Your Infrastructure Affected by CVE-2025-53098?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs