Security feature bypass via undisclosed untrusted functionality
Published Jul 14, 2026 · Updated Jul 14, 2026
Security feature bypass in Microsoft Visual Studio Code before 1.128.1 allows remote attackers to defeat a protection through network content. Microsoft identifies inclusion of functionality from an untrusted control sphere but does not disclose the affected feature, code locus, or incorrect operation. Exploitation requires user interaction; the published assessment covers disclosure, modification, and service interruption without identifying the protected resources.
Summary
What happened
Security feature bypass in Microsoft Visual Studio Code before 1.128.1 allows remote attackers to defeat a protection through network content. Microsoft identifies inclusion of functionality from an untrusted control sphere but does not disclose the affected feature, code locus, or incorrect operation. Exploitation requires user interaction; the published assessment covers disclosure, modification, and service interruption without identifying the protected resources.
The record
- CVE
- CVE-2026-57102
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-200, CWE-829
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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.128.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