CVE-2026-81837

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-08-28. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A flaw has been found in RooCodeInc Roo-Code up to 3.51.1." No release containing a fix is confirmed on record.

A flaw has been found in RooCodeInc Roo-Code up to 3.51.1. This issue affects the function path.resolve of the file src/core/tools/ApplyPatchTool.ts of the component ApplyPatchTool. This manipulation causes path traversal. It is possible to initiate the attack remotely. The exploit has been published and may be used. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No fix on record yet.
Web page

Roo-Code v3.51.1 - Path Traversal Advisory · GitHub

https://gist.github.com/tchen200311/c5b8eeb9b7f8e4e6f19e7432d7bb1e31

Vendor Advisories for CVE-2026-81837(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 78× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 134 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81837?
CVE-2026-81837 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. A flaw has been found in RooCodeInc Roo-Code up to 3.51.1. This issue affects the function path.resolve of the file src/core/tools/ApplyPatchTool.ts of the component ApplyPatchTool. This manipulation causes path traversal. It is possible to initiate the attack remotely. The exploit has been…
When was the CVE record for CVE-2026-81837 published?
The CVE record for CVE-2026-81837 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-81837 actively exploited?
CVE-2026-81837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81837?
CVE-2026-81837 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81837?
No fix for CVE-2026-81837 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A flaw has been found in RooCodeInc Roo-Code up to 3.51.1." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-81837 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81837

Explore →

Is Your Infrastructure Affected by CVE-2026-81837?

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

Book a Demo →Browse All CVEs