Visual Studio Code vulnerabilities: known CVEs & security history
Microsoft · Developer Tools · 41 tracked CVEs · 0 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Visual Studio Code release lines — 41 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.
Known Visual Studio Code CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-81376 | critical | 9.6 | 1% | 2026 |
| CVE-2026-47281 | critical | 9.6 | 1% | 2026 |
| CVE-2026-78462 | high | 8.8 | 1% | 2026 |
| CVE-2026-70336 | high | 8.8 | 1% | 2026 |
| CVE-2026-69320 | high | 8.8 | 0% | 2026 |
| CVE-2026-59113 | high | 8.8 | 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-81379 | high | 8.2 | 0% | 2026 |
| CVE-2026-81378 | high | 8.2 | 0% | 2026 |
| CVE-2026-81357 | high | 8.2 | 0% | 2026 |
| CVE-2026-81356 | high | 8.2 | 0% | 2026 |
| CVE-2026-69306 | high | 8.2 | 0% | 2026 |
| CVE-2026-70334 | high | 7.8 | 0% | 2026 |
| CVE-2026-70335 | high | 7.8 | 0% | 2026 |
| CVE-2026-69278 | high | 7.8 | 0% | 2026 |
| CVE-2026-58650 | high | 7.8 | 0% | 2026 |
| CVE-2026-54981 | high | 7.8 | 0% | 2026 |
| CVE-2026-47292 | high | 7.8 | 0% | 2026 |
| CVE-2021-42322 | high | 7.8 | 0% | 2021 |
| CVE-2021-34529 | high | 7.8 | 4% | 2021 |
| CVE-2021-34528 | high | 7.8 | 3% | 2021 |
| CVE-2021-34479 | high | 7.8 | 3% | 2021 |
| CVE-2021-27060 | high | 7.8 | 3% | 2021 |
| CVE-2026-40376 | high | 7.5 | 1% | 2026 |
| CVE-2026-81383 | high | 7.4 | 1% | 2026 |
| CVE-2026-78461 | high | 7.4 | 1% | 2026 |
| CVE-2026-65675 | high | 7.1 | 0% | 2026 |
| CVE-2026-57101 | high | 7.1 | 0% | 2026 |
| CVE-2026-48569 | high | 7.1 | 0% | 2026 |
| CVE-2026-81381 | medium | 6.5 | 1% | 2026 |
| CVE-2026-81377 | medium | 6.5 | 1% | 2026 |
| CVE-2026-47285 | medium | 6.5 | 1% | 2026 |
| CVE-2026-47282 | medium | 6.5 | 1% | 2026 |
| CVE-2026-50519 | 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 |
| CVE-2021-26437 | medium | 5.5 | 2% | 2021 |
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 41 CVEs for Visual Studio Code. 2 are critical-severity and 30 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-81376 (CRITICAL, CVSS 9.6) ranks highest — a CWE-693 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.