# CVE-2025-58373: Roo Code: Symlink-bypass of .rooignore can lead to unintended file disclosure

> Attackers with workspace write access can bypass .rooignore via symlinks to disclose sensitive files like secrets and configurations.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-p76r-7mc3-qh7c

## What is CVE-2025-58373?

CVE-2025-58373 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 5 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Roo Code is an AI-powered autonomous coding agent that lives in users' editors. Versions 3.25.23 and below contain a vulnerability where .rooignore protections could be bypassed using symlinks. This allows an attacker with write access to the workspace to trick the extension into reading files that were intended to be excluded. As a result, sensitive files such as .env or configuration files could be exposed. An attacker able to modify files within the workspace could gain unauthorized access to sensitive information by bypassing .rooignore rules. This could include secrets, configuration details, or other excluded project data. This is fixed in version 3.26.0.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2025-58373?

It affects 1 product.


Products: Roocode Roo Code.

## How do I fix CVE-2025-58373?

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

## Is CVE-2025-58373 being exploited?

There is no known exploitation of CVE-2025-58373 in the wild and no public exploit code.

## Other vulnerabilities in RooCodeInc Roo-Code

- [CVE-2025-58371](https://insights.sbomify.com/CVE-2025-58371/): Roo Code is vulnerable to command injection via GitHub actions workflow (critical 9.9)
- [CVE-2026-30307](https://insights.sbomify.com/CVE-2026-30307/): Command injection in n/a (critical 9.8)
- [CVE-2025-65946](https://insights.sbomify.com/CVE-2025-65946/): Roo Code is Vulnerable to Potential Remote Code Execution via zsh Command Validation Bug (high 8.1)
- [CVE-2025-58370](https://insights.sbomify.com/CVE-2025-58370/): Roo Code: Potential Remote Code Execution via Bash Parameter Expansion and Indirect Reference (high 8.1)
- [CVE-2025-58372](https://insights.sbomify.com/CVE-2025-58372/): Roo Code: Potential Remote Code Execution via .code-workspace (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58373 and fix it if it is affected.

What it is: CVE-2025-58373 is a medium-severity path traversal vulnerability in RooCodeInc Roo-Code, published on 5 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-58373 in the wild and no public exploit code.

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

## Sources

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

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