Local file and directory exposure
Published May 13, 2025 · Updated Feb 13, 2026
Security feature bypass in VS Code before 1.100.1 and Copilot Chat before 0.27.2 allows attackers to access protected local files. Microsoft has not disclosed the affected file-handling locus or the operation that incorrectly makes files or directories externally accessible. Exploitation is local and requires user interaction; successful use crosses a security boundary, exposing data and permitting limited modification without interrupting service.
Summary
What happened
Security feature bypass in VS Code before 1.100.1 and Copilot Chat before 0.27.2 allows attackers to access protected local files. Microsoft has not disclosed the affected file-handling locus or the operation that incorrectly makes files or directories externally accessible. Exploitation is local and requires user interaction; successful use crosses a security boundary, exposing data and permitting limited modification without interrupting service.
The record
- CVE
- CVE-2025-21264
- Published
- May 13, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-552
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record 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=1.0.0 <1.100.1
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