CVE-2026-121661: Microsoft Visual Studio Code security feature bypass

CVE-2026-121661 · Severity: high · CVSS 7.8 · Published 2026-11-10

Visual Studio Code, a widely-used code editor, contains an incomplete filter that allows a local attacker to bypass a security feature designed to block malicious inputs. An attacker with local access could circumvent protections intended to prevent execution of dangerous commands or scripts.

Technologies: Microsoft Visual Studio Code. Vendors: Microsoft.

Quick answers

Is CVE-2026-121661 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-121661 being exploited in the wild.
How severe is CVE-2026-121661?
High severity, with a CVSS score of 7.8, published 10 November 2026.
Which products and versions are affected?
Microsoft Visual Studio Code.
Is there a fix for CVE-2026-121661?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-121661 attacked?
It is attacked with local access.
Am I affected by CVE-2026-121661?
Check whether you run Microsoft Visual Studio Code. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Visual Studio Code implements an input validation filter to prevent execution of dangerous inputs; however, the list of disallowed patterns is incomplete, allowing an attacker to craft inputs that evade the filter. The vulnerability requires local access to the affected system. An attacker can bypass the security feature to execute unauthorized actions.

Affected products

  • Microsoft Visual Studio Code

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.