CVE-2022-35826: Visual Studio Remote Code Execution Vulnerability

Published Aug 9, 2022
·
Updated

Visual Studio Remote Code Execution Vulnerability

Affected Software

16 affected componentsFixes available
Microsoft Visual Studio 2012=5
Patch available
Microsoft Visual Studio 2019 (includes 16.0 - 16.8)=16.9
Patch available
Microsoft Visual Studio 2019 (includes 16.0 - 16.10)=16.11
Patch available
Microsoft Visual Studio 2017 (includes 15.0 - 15.8)=15.9
Patch available
Microsoft Visual Studio 2015=3
Patch available
Microsoft Visual Studio 2013=5
Patch available
Microsoft Visual Studio=2012-update_5
Microsoft Visual Studio=2013-update_5
Microsoft Visual Studio=2015-update3
Microsoft Visual Studio 2017=15.9
Microsoft Visual Studio 2019=16.9
Microsoft Visual Studio 2019=16.11
Microsoft Visual Studio 2022=17.0
Microsoft Visual Studio 2022=17.2
Microsoft Visual Studio 2022=17.2
Patch available
Microsoft Visual Studio 2022=17.0
Patch available

Event History

Aug 9, 2022
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·08:12 PM
Data Sourced
via MITRE·08:12 PM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-35826?

CVE-2022-35826 is a visual Studio remote code execution vulnerability.

2

How severe is CVE-2022-35826?

CVE-2022-35826 has a severity rating of 8.8 (high).

3

Which versions of Visual Studio are affected by CVE-2022-35826?

Visual Studio 2012, Visual Studio 2015, Visual Studio 2019 (16.0 - 16.8), Visual Studio 2017 (15.0 - 15.8), Visual Studio 2013, Visual Studio 2019 (16.0 - 16.10), Visual Studio 2022 (17.0), Visual Studio 2022 (17.2) are affected by CVE-2022-35826.

4

How do I fix CVE-2022-35826 in Visual Studio 2012?

To fix CVE-2022-35826 in Visual Studio 2012, update to version 5.

5

How do I fix CVE-2022-35826 in Visual Studio 2015?

To fix CVE-2022-35826 in Visual Studio 2015, update to version 3.

6

How do I fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.8)?

To fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.8), refer to the Microsoft support page for the specific remedy.

7

How do I fix CVE-2022-35826 in Visual Studio 2017 (15.0 - 15.8)?

To fix CVE-2022-35826 in Visual Studio 2017 (15.0 - 15.8), refer to the Microsoft support page for the specific remedy.

8

How do I fix CVE-2022-35826 in Visual Studio 2013?

To fix CVE-2022-35826 in Visual Studio 2013, update to version 5.

9

How do I fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.10)?

To fix CVE-2022-35826 in Visual Studio 2019 (16.0 - 16.10), refer to the Microsoft support page for the specific remedy.

10

How do I fix CVE-2022-35826 in Visual Studio 2022 (17.0)?

To fix CVE-2022-35826 in Visual Studio 2022 (17.0), refer to the Microsoft support page for the specific remedy.

11

How do I fix CVE-2022-35826 in Visual Studio 2022 (17.2)?

To fix CVE-2022-35826 in Visual Studio 2022 (17.2), refer to the Microsoft support page for the specific remedy.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203