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.
CVE-2026-81837
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.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026Roo-Code v3.51.1 - Path Traversal Advisory · GitHub
https://gist.github.com/tchen200311/c5b8eeb9b7f8e4e6f19e7432d7bb1e31Vendor 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 16× in last 7d / 16× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:41 UTCEG score recompute
- 2026-08-29 19:41 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:40 UTCEG score recompute
- 2026-08-28 20:39 UTCGHSA enrichment
- 2026-08-28 20:24 UTCNVD updateCVSS v4 → 2.1
- 2026-08-28 19:46 UTCEG score recompute
- 2026-08-28 19:46 UTCGHSA enrichment
- 2026-08-28 19:36 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-08-28 15:18 UTCEG score recompute
- 2026-08-28 15:17 UTCGHSA enrichment
- 2026-08-28 00:31 UTCEG score recompute
- 2026-08-28 00:26 UTCNVD updateCVSS v4 → 2.1
- 2026-08-27 23:23 UTCEG score recompute
- 2026-08-27 23:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81837?
When was CVE-2026-81837 disclosed?
Is CVE-2026-81837 actively exploited?
What is the CVSS score of CVE-2026-81837?
How do I remediate CVE-2026-81837?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81837
Is Your Infrastructure Affected by CVE-2026-81837?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.