Security feature bypass via unvalidated AI output
Published Nov 11, 2025 · Updated Nov 11, 2025
Improper output validation in Microsoft Visual Studio Code before 1.105.0 allows local users to bypass a security feature. Microsoft identifies generative AI output from GitHub Copilot as the untrusted input, but has not disclosed the affected code locus or the validation operation that fails. Exploitation requires low privileges and user interaction and can compromise integrity, with no reported confidentiality or availability impact.
Summary
What happened
Improper output validation in Microsoft Visual Studio Code before 1.105.0 allows local users to bypass a security feature. Microsoft identifies generative AI output from GitHub Copilot as the untrusted input, but has not disclosed the affected code locus or the validation operation that fails. Exploitation requires low privileges and user interaction and can compromise integrity, with no reported confidentiality or availability impact.
The record
- CVE
- CVE-2025-62453
- Published
- Nov 11, 2025
- Updated
- Nov 11, 2025
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-693, CWE-1426
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 11, 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=1.0.0 <1.105.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