59/59 sources · synced 00:50 UTC Customize Public mode
CVE-2026-81379ImportantRevised 11 Sep

Visual Studio Code Security Feature Bypass Vulnerability

MSRC advisory NVD CVE.org

Assessment

Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

Severity
Important
CVSS base score
8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C
Impact
Security Feature Bypass
EPSS, next 30 days
0.5%Higher than 43.2% of scored CVEs · FIRST model run 26 Sep 2026 · about EPSS
Exploitability
Exploitation Less Likely
Publicly disclosed
No
Customer action
Required: apply the update
Component
Visual Studio Code
Weakness
CWE-636: Not Failing Securely ('Failing Open')
Issued by
Microsoft
Published
8 Sep 2026 · September 2026
Last revised
11 Sep 2026Updated an acknowledgement. This is an informational change only.

Updates that fix it

0 KBs

No KB listed

MSRC lists no downloadable update, which usually means a service-side fix or a release-notes update. Check the MSRC advisory.

Affected products

Developer Tools
1 affected product
  • Visual Studio Code
ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft. Microsoft, Windows, Microsoft 365, Azure, and related names are trademarks of the Microsoft group of companies. Data comes from public sources listed on Sources; every item links to its original page. Dates and statuses can change after they are read. Built by Evotec. This is the public demo. It can also run on your own server, with your Microsoft 365 tenant and device data kept inside your network; Evotec can help you deploy and extend it.