Visual Studio Code CVE-2026-41613

Exploitation requires a network-reachable Visual Studio Code session/authentication path (consistent with remote tunnel, remote-SSH, or web-served session usage) and mandatory victim interaction (CVSS UI:R) - the target user must be induced to open or authenticate against an attacker-influenced session identifier. No prior authentication or privileges are needed on the attacker's side (PR:N). Limiting factors that reduce realistic risk: the attack cannot be fully automated (SSVC Automatable: no), it depends on the victim taking a specific action, and installations that do not use network-facing session/remote features present a smaller attack surface. Affected only on Visual Studio Code versions 1.0.0 through <1.119.1.

The signals are mixed and should be read together rather than off the raw 8.8. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates a network-reachable, low-complexity, unauthenticated attack - but the mandatory UI:R (user interaction) means a victim must be induced to act, which materially lowers real-world exploitability and aligns with SSVC's 'Automatable: no'. SSVC also records 'Exploitation: none', and EPSS is very low at 0.06% (18th percentile), so there is no evidence of active or imminent mass exploitation; the high score is driven by the 'Technical Impact: total' (full C/I/A compromise of the affected session). There is no KEV listing and no POC reference, so this reads as a genuinely high-impact-if-triggered issue that is not currently a mass-exploitation priority - patch on a normal-to-prompt cycle rather than emergency. One caveat to verify: the description frames this as 'elevate privileges over a network' while session fixation typically also requires the attacker to first plant a session identifier and the victim to authenticate - confirm the exact triggering path with Microsoft's advisory, as the AC:L rating may understate the setup required.

An attacker pre-establishes or plants a known session identifier and then socially engineers a developer into opening a crafted VS Code session, tunnel, or link (satisfying the UI:R requirement). Once the victim authenticates, the attacker reuses the fixated session token to assume the victim's authenticated context over the network, gaining full read/write control of that session. No public exploit code has been identified at time of analysis, so this remains a plausible-but-unproven attack path.