Excluded-file disclosure via unresolved workspace symlinks
Published Sep 5, 2025 · Updated Sep 8, 2025
Improper link resolution in Roo Code before 3.26.0 allows local users to read excluded workspace files through a crafted symlink. RooIgnoreController.validateAccess checks the supplied workspace path against .rooignore rules without first resolving its symlink target, so an allowed link can reach an ignored file. Exploitation requires workspace write access and user interaction that causes Roo Code to access the link, exposing only files readable by the editor process.
Summary
What happened
Improper link resolution in Roo Code before 3.26.0 allows local users to read excluded workspace files through a crafted symlink. RooIgnoreController.validateAccess checks the supplied workspace path against .rooignore rules without first resolving its symlink target, so an allowed link can reach an ignored file. Exploitation requires workspace write access and user interaction that causes Roo Code to access the link, exposing only files readable by the editor process.
The record
- CVE
- CVE-2025-58373
- Published
- Sep 5, 2025
- Updated
- Sep 8, 2025
- Vendor
- Roo Code, Inc.
- Product
- Roo Code
- Classifications
- CWE-59, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.26.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo