# CVE-2026-81837: RooCodeInc Roo-Code ApplyPatchTool ApplyPatchTool.ts path.resolve path traversal

> Remote attackers can exploit path traversal in Roo Code's ApplyPatchTool to read or modify arbitrary files, affecting an unsupported project.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-pjx2-9jx7-x89r

## What is CVE-2026-81837?

CVE-2026-81837 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-81837?


## How do I fix CVE-2026-81837?

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

## Is CVE-2026-81837 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81837 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81837 and fix it if it is affected.

What it is: CVE-2026-81837 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81837 exists.

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-2026-81837/ (Markdown: https://insights.sbomify.com/CVE-2026-81837/index.md)
```

## Sources

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

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