Microsoft Visual Studio Code: Security feature bypass via incomplete input filtering

Summary

Visual Studio Code contains a security feature bypass vulnerability (CWE-184). The list of disallowed inputs is incomplete, so a crafted input can get past the protection. An unauthorized attacker with local access can exploit this, but user interaction is required, for example by opening a crafted file or project. Successful exploitation may affect confidentiality, integrity and availability, according to the CVSS vector.

Affected

• Microsoft Visual Studio Code from 1.0.0 before 1.145.3 (per CNA data; to be confirmed against the MSRC advisory)

Fixed in

• Fixed in Visual Studio Code 1.145.3
• Delivery method (auto-update or system installer) unknown.

Workaround

• No workaround known. Update to 1.145.3 or later.

Exploitation

• Microsoft rates exploitation as less likely.
• Not publicly disclosed at the time of research.
• Not listed in the CISA KEV catalog.
• No public proof of concept found.

Our recommendation

• Inventory all Visual Studio Code installations, including per-user installs that may not update centrally.
• Update to version 1.145.3 or later in the regular monthly patch cycle.
• Prioritise developer workstations and systems where untrusted users have local access.
• Check NVD and the MSRC advisory again once analysis is published, as the affected range and CVSS may change.

Public exploits iAttack code is publicly available (PoC on GitHub, Metasploit or Exploit-DB).

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

• Microsoft Security Update Guide: CVE-2026-121661 msrc.microsoft.com
• Strix: CVE-2026-121661 www.strix.ai
• Visual Studio Code 1.145 release notes code.visualstudio.com
• Rapid7: Microsoft Patch Tuesday November 2026 www.rapid7.com

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 03:33.