Visual Studio Code CVE-2026-81356

User interaction is required (UI:R) - the attack is triggered when the targeted developer opens a malicious workspace, file, or URL within VS Code, or connects to an attacker-influenced server endpoint. No authentication or elevated privileges are required from the attacker (PR:N). The attack is network-delivered (AV:N) with low complexity (AC:L), meaning no race conditions or special environmental state are needed beyond the triggering interaction. Exploitation is bounded by: (1) the victim must be running an affected VS Code release (< 1.136.2); (2) the victim must perform some qualifying user interaction; and (3) a reachable downstream HTTP component must interpret request boundaries differently from VS Code. Specific VS Code features exposing HTTP endpoints (Remote Tunnels, Live Preview, extension host) are likely prerequisites but are not named explicitly in the advisory.

The CVSS 8.2 score is driven primarily by the network attack vector, lack of required privileges, and a scope change that elevates confidentiality impact to High. The UI:R modifier limits fully automated mass exploitation, though even a mid-sized municipal IT team in ustka should treat this as urgent given the ubiquity of VS Code installations and the potential for high-value credential or token exfiltration through smuggled requests. No exploitation has been confirmed by CISA KEV, and no public proof-of-concept has been identified at time of analysis, which moderates immediate alarm somewhat. However, HTTP request smuggling vulnerabilities historically attract rapid weaponization once technical details circulate, and the AC:L metric suggests no unusual environmental prerequisites beyond network reachability and a triggering user interaction. The absence of an EPSS score in the provided data means probabilistic exploitation likelihood cannot be independently quantified here; defenders should monitor for KEV updates.

An attacker serving a malicious web page or workspace file induces a developer's VS Code instance to issue or relay an HTTP request containing ambiguous Content-Length and Transfer-Encoding headers to a back-end service. The back-end interprets a smuggled secondary request as originating from the trusted VS Code client, bypassing authentication or authorization checks and exposing sensitive data such as tokens, session cookies, or internal API responses.