CVE-2021-1680 [High] | Privilege Escalation in Visual Studio

CVE-2021-1680 is rated Moderate Risk (48.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.26%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-01-05	0.19%	0.26%	+0.07%
2	2025-12-02	0.35%	0.19%	-0.16%
3	2025-05-20	—	0.35%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-05

0.19%

0.26%

+0.07%

2025-12-02

0.35%

0.19%

-0.16%

2025-05-20

—

0.35%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]
4.6	2.0	MEDIUM	`AV:L/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	3.9	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

4.6

2.0

MEDIUM

AV:L/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

3.9

6.4

[email protected]

Affected software / configurations for CVE-2021-1680

Vendor	Product	Version	Raw CPE
microsoft	visual_studio	2015	cpe:2.3:a:microsoft:visual_studio:2015:update3::::::
microsoft	visual_studio_2017	>= 15.0, <= 15.8	cpe:2.3:a:microsoft:visual_studio_2017::::::::
microsoft	visual_studio_2019	>= 16.0, <= 16.7.0	cpe:2.3:a:microsoft:visual_studio_2019::::::::
microsoft	visual_studio_2019	16.8	cpe:2.3:a:microsoft:visual_studio_2019:16.8:::::::*
microsoft	windows_10	—	cpe:2.3:o:microsoft:windows_10:-:::::::*
microsoft	windows_10	20h2	cpe:2.3:o:microsoft:windows_10:20h2:::::::*
microsoft	windows_10	1607	cpe:2.3:o:microsoft:windows_10:1607:::::::*
microsoft	windows_10	1803	cpe:2.3:o:microsoft:windows_10:1803:::::::*
microsoft	windows_10	1809	cpe:2.3:o:microsoft:windows_10:1809:::::::*
microsoft	windows_10	1909	cpe:2.3:o:microsoft:windows_10:1909:::::::*
microsoft	windows_10	2004	cpe:2.3:o:microsoft:windows_10:2004:::::::*
microsoft	windows_server_2016	—	cpe:2.3:o:microsoft:windows_server_2016:-:::::::*
microsoft	windows_server_2016	20h2	cpe:2.3:o:microsoft:windows_server_2016:20h2:::::::*
microsoft	windows_server_2016	1909	cpe:2.3:o:microsoft:windows_server_2016:1909:::::::*
microsoft	windows_server_2016	2004	cpe:2.3:o:microsoft:windows_server_2016:2004:::::::*
microsoft	windows_server_2019	—	cpe:2.3:o:microsoft:windows_server_2019:-:::::::*

References for CVE-2021-1680

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1680
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-1680

URL

CVE-2021-1680 | Diagnostics Hub Standard Collector Elevation of Privilege Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2021-1680

Common vulnerability scoring system (CVSS) metrics for CVE-2021-1680

Weakness enumeration for CVE-2021-1680

Affected software / configurations for CVE-2021-1680

References for CVE-2021-1680