Visual Studio Code CVE-2026-81376

Requires victim user interaction (CVSS UI:R): a developer must open or interact with attacker-controlled content in an affected VS Code build (1.0.0 through <1.136.2) - for example a malicious workspace/repository, crafted file, or untrusted URI handled by the editor. No authentication or prior privileges are needed (PR:N), and the vector is network-delivered (AV:N) with low complexity (AC:L), but exploitation is limited by the need for that user action and by the target running a version before 1.136.2. The exact security feature being bypassed is not disclosed in the terse MSRC description.

The signals are mostly aligned toward high priority: CVSS 9.6 with AV:N/AC:L/PR:N reflects an unauthenticated, low-complexity network vector, and S:C with C:H/I:H/A:H implies the bypass crosses a security boundary into broader impact - plausible for an editor that can execute tasks or extensions. The key limiter is UI:R: exploitation requires a victim to open or interact with attacker-supplied content (a crafted workspace, repository, file, or link), so this is a social-engineering-gated bug rather than a wormable server flaw. No EPSS score, KEV listing, or POC was provided, so there is no evidence of active exploitation or automated weaponization at this time; the risk is real but currently inferred from CVSS and the vendor's high rating rather than observed attacks. Given VS Code's massive developer footprint, any organization running affected builds should patch promptly, but the UI:R gate means realistic exploitation depends on tricking a developer into opening malicious content. Note a data caveat: the description is Microsoft's terse MSRC boilerplate ('bypass a security feature over a network'), so the exact protected feature and the C:H/I:H/A:H mapping cannot be independently verified - confirm specifics against the MSRC advisory.

An attacker publishes a booby-trapped repository or workspace (or sends a crafted file or vscode:// deep link) and lures a developer into opening it in an unpatched VS Code build. The incomplete comparison causes the relevant security feature to be bypassed, and with the scope-changed high-impact profile the attacker can reach protected functionality - potentially leading to code execution or data compromise on the developer's machine. No public exploit is identified at time of analysis.