CVE-2025-53536

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 52% 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: 0.8%CVSS: 8.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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%
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

Published

July 7, 2025

Last Modified

September 15, 2025

Advisory Details (3)

Auto-updated Sep 9, 2026
Fix named in the CVE record. Sources: github_commit, github.
githubMentions a patch (unverified)

Potential Remote Code Execution via .vscode/settings.json in the Roo Code extension · Advisory · RooCodeInc/Roo-Code · GitHub

https://github.com/RooCodeInc/Roo-Code/security/advisories/GHSA-3765-5vjr-qjgm
github_commit

commit 3993406ebdc0 (RooCodeInc/Roo-Code)

Fix landed in RooCodeInc/Roo-Code commit 3993406ebdc0 — awaiting tagged release

https://github.com/RooCodeInc/Roo-Code/commit/3993406ebdc0553a32ef391a799a4fb124930a1c
github_commit

commit 1be6fce1a686 (RooCodeInc/Roo-Code)

Fix landed in RooCodeInc/Roo-Code commit 1be6fce1a686 — awaiting tagged release

https://github.com/RooCodeInc/Roo-Code/commit/1be6fce1a6864ae63e8160b0666db2c647f2dbba

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× 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 172 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-53536?
CVE-2025-53536 is a high vulnerability published on July 7, 2025. 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…
When was CVE-2025-53536 disclosed?
CVE-2025-53536 was first published on July 7, 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-53536 actively exploited?
CVE-2025-53536 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-53536?
CVE-2025-53536 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-53536?
The CVE record for CVE-2025-53536 names the fix: "This vulnerability is fixed in 3.22.6."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-53536?

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