CVE-2026-119981: Microsoft Visual Studio Code missing authentication in critical function

CVE-2026-119981 · Severity: high · CVSS 7 · Published 2026-11-10

Visual Studio Code is a widely-used code editor that developers rely on for application development. This vulnerability allows an authorized user with local access to bypass authentication controls and gain elevated privileges on the affected system, potentially leading to data theft or malware installation.

Technologies: Microsoft Visual Studio Code. Vendors: Microsoft.

Quick answers

Is CVE-2026-119981 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-119981 being exploited in the wild.
How severe is CVE-2026-119981?
High severity, with a CVSS score of 7, published 10 November 2026.
Which products and versions are affected?
Microsoft Visual Studio Code.
Is there a fix for CVE-2026-119981?
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-119981 attacked?
It is attacked with local access.
Am I affected by CVE-2026-119981?
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

A critical function in Visual Studio Code lacks proper authentication checks, allowing a locally authenticated attacker to escalate privileges. The vulnerability requires local access and existing user authentication, but once exploited grants elevated system privileges. A fix has been released by Microsoft.

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.