How severe is CVE-2021-1639?

CVE-2021-1639 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2021-1639 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2021-1639?

CVE-2021-1639 primarily affects Microsoft Visual Studio 2017. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2021-1639?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2021-1639 published?

CVE-2021-1639 was published on 2021-02-25 and last updated on 2026-06-17.

CVE-2021-1639

CVE-2021-1639 is a high-severity vulnerability in Microsoft Visual Studio 2017 with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.0)
CVSS v2: 6.8
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft Visual Studio 2017
Published: 2021-02-25
Last modified: 2026-06-17

Description

Visual Studio Code Remote Code Execution Vulnerability

Frequently asked questions

What is CVE-2021-1639?: Visual Studio Code Remote Code Execution Vulnerability
How severe is CVE-2021-1639?: CVE-2021-1639 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2021-1639 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-1639?: CVE-2021-1639 primarily affects Microsoft Visual Studio 2017. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2021-1639?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2021-1639 published?: CVE-2021-1639 was published on 2021-02-25 and last updated on 2026-06-17.

References

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-1639

Affected products (3)

cpe:2.3:a:microsoft:visual_studio_2017:*:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:visual_studio_code:-:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Visual Studio 2017

CVE-2025-49739 — High (CVSS 8.8): Improper link resolution before file access ('link following') in Visual Studio allows an unauthorized attacker to…
CVE-2025-21178 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2025-21176 — High (CVSS 8.8): .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability
CVE-2022-35827 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2022-35826 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability
CVE-2022-35825 — High (CVSS 8.8): Visual Studio Remote Code Execution Vulnerability

All CVEs affecting Microsoft Visual Studio 2017 →