Skip to content
Fencer Vulns
high 8.8

CVE-2022-35825 json

Visual Studio Remote Code Execution Vulnerability

published 2022-08-09 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-38698

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

Visual Studio Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.50
  • Microsoft Microsoft Visual Studio 2019 version 16.9 (includes 16.0 - 16.8) 16.9.24
  • Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.18
  • Microsoft Microsoft Visual Studio 2022 version 17.0 17.0.13
  • Microsoft Microsoft Visual Studio 2012 Update 5 11.0.61252.0
  • Microsoft Microsoft Visual Studio 2013 Update 5 12.0.40699.0
  • Microsoft Microsoft Visual Studio 2015 Update 3 14.0.27552.0
  • Microsoft Microsoft Visual Studio 2022 version 17.2 17.2.7

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
  • Microsoft Microsoft Visual Studio 2019 version 16.9 (includes 16.0 - 16.8)
  • Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
  • Microsoft Microsoft Visual Studio 2022 version 17.0
  • Microsoft Microsoft Visual Studio 2012 Update 5
  • Microsoft Microsoft Visual Studio 2013 Update 5
  • Microsoft Microsoft Visual Studio 2015 Update 3
  • Microsoft Microsoft Visual Studio 2022 version 17.2

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.