Local security bypass through relative path traversal
Published Jun 9, 2026 · Updated Jun 9, 2026
Improper input validation in Microsoft Visual Studio Code before 1.123.2 allows local users to bypass a security feature. Microsoft maps the flaw to relative path traversal but has not disclosed the affected component, the rejected path form, or the validation operation. Exploitation requires user interaction without prior privileges and can expose protected data and make limited modifications outside the editor's security scope.
Summary
What happened
Improper input validation in Microsoft Visual Studio Code before 1.123.2 allows local users to bypass a security feature. Microsoft maps the flaw to relative path traversal but has not disclosed the affected component, the rejected path form, or the validation operation. Exploitation requires user interaction without prior privileges and can expose protected data and make limited modifications outside the editor's security scope.
The record
- CVE
- CVE-2026-48569
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-20, CWE-23, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 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.119.1
What conditions does exploitation require?
What is affected?
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