Synced 03 Aug 2026 05:54 UTC Account
← Visual Studio Code

Visual Studio Code vulnerabilities: known CVEs & security history

Microsoft · Developer Tools · 13 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Visual Studio Code release lines — 13 in total. A CVE here doesn't mean your version is affected — check Visual Studio Code's current status and the safe version to run.

13
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known Visual Studio Code CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-47281 critical 9.6 1% 2026
CVE-2026-57102 high 8.8 1% 2026
CVE-2026-41109 high 8.8 1% 2026
CVE-2026-50520 high 8.4 1% 2026
CVE-2026-45482 high 8.4 0% 2026
CVE-2026-47292 high 7.8 0% 2026
CVE-2026-40376 high 7.5 1% 2026
CVE-2026-57101 high 7.1 0% 2026
CVE-2026-48569 high 7.1 0% 2026
CVE-2026-47282 medium 6.5 1% 2026
CVE-2026-47287 medium 6.5 1% 2026
CVE-2026-47284 medium 6.5 1% 2026
CVE-2026-45496 medium 5.5 0% 2026

Is my Visual Studio Code version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Visual Studio Code version → · Monitor Visual Studio Code for new CVEs →

Visual Studio Code vulnerabilities — frequently asked

How many known vulnerabilities does Visual Studio Code have?

IsItPatched tracks 13 CVEs for Visual Studio Code. 1 is critical-severity and 8 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Visual Studio Code have any actively-exploited vulnerabilities?

None of Visual Studio Code's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Visual Studio Code vulnerability?

Among tracked issues, CVE-2026-47281 (CRITICAL, CVSS 9.6) ranks highest — a Missing authentication weakness.

Is Visual Studio Code safe to use?

It depends on the version. The latest supported Visual Studio Code release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Visual Studio Code security status · Visual Studio Code end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.