CVE-2026-105016 |
critical
|
9.8 |
0.0166
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-88092 |
critical
|
9.4 |
0.0093
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-88092 |
critical
|
9.4 |
0.0093
|
microsoft |
visual_studio_2022 |
< 17.14.42
|
|
CVE-2026-70188 |
critical
|
9.1 |
0.0094
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
microsoft |
visual_studio_2022 |
< 17.14.36
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
microsoft |
visual_studio_2022 |
< 17.14.36
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-47300 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-47303 |
high
|
8.8 |
0.0084
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-102869 |
high
|
8.8 |
0.0084
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-102870 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.43
|
|
CVE-2026-70007 |
high
|
8.8 |
0.0080
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-70035 |
high
|
8.8 |
0.0143
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-83520 |
high
|
8.8 |
0.0143
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-85363 |
high
|
8.8 |
0.0086
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-96230 |
high
|
8.8 |
0.0095
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-96235 |
high
|
8.8 |
0.0086
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-96957 |
high
|
8.8 |
0.0053
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-103572 |
high
|
8.8 |
0.0099
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-70174 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-87697 |
high
|
8.8 |
0.0084
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-96224 |
high
|
8.8 |
0.0076
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-96957 |
high
|
8.8 |
0.0053
|
microsoft |
visual_studio_2022 |
< 17.14.42
|
|
CVE-2026-50528 |
high
|
8.2 |
0.0061
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-50528 |
high
|
8.2 |
0.0061
|
microsoft |
visual_studio_2022 |
< 17.14.36
|
|
CVE-2026-50528 |
high
|
8.2 |
0.0061
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-50528 |
high
|
8.2 |
0.0061
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-47304 |
high
|
8.1 |
0.0029
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-47304 |
high
|
8.1 |
0.0029
|
microsoft |
visual_studio_2022 |
< 17.14.36
|
|
CVE-2026-47304 |
high
|
8.1 |
0.0029
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-47304 |
high
|
8.1 |
0.0029
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-70175 |
high
|
8.1 |
0.0073
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.42
|
|
CVE-2026-70197 |
high
|
8.1 |
0.0079
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.43
|
|
CVE-2026-50646 |
high
|
7.8 |
0.0402
|
microsoft |
visual_studio_2022 |
< 17.12.22
|
|
CVE-2026-50646 |
high
|
7.8 |
0.0402
|
microsoft |
visual_studio_2022 |
< 17.14.36
|
|
CVE-2026-62871 |
high
|
7.8 |
0.0047
|
microsoft |
visual_studio_2022 |
< 17.14.38
|
|
CVE-2026-62886 |
high
|
7.8 |
0.0047
|
microsoft |
visual_studio_2022 |
< 17.14.38
|
|
CVE-2026-62909 |
high
|
7.8 |
0.0026
|
microsoft |
visual_studio_2022 |
< 17.14.38
|
|
CVE-2026-70354 |
high
|
7.8 |
0.0036
|
microsoft |
visual_studio_2022 |
< 17.14.38
|
|
CVE-2026-62871 |
high
|
7.8 |
0.0047
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.38
|
|
CVE-2026-70354 |
high
|
7.8 |
0.0036
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.38
|
|
CVE-2026-47305 |
high
|
7.8 |
0.0047
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-47305 |
high
|
7.8 |
0.0047
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-50646 |
high
|
7.8 |
0.0402
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-50646 |
high
|
7.8 |
0.0402
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|
CVE-2026-50650 |
high
|
7.8 |
0.0046
|
Microsoft |
Microsoft Visual Studio 2022 version 17.12 |
17.12.0
< 17.12.22
|
|
CVE-2026-50650 |
high
|
7.8 |
0.0046
|
Microsoft |
Microsoft Visual Studio 2022 version 17.14 |
17.14.0
< 17.14.36
|
|