Skip to main content
VulnerabilityPublished Updated

CVE-2022-34716: Microsoft Visual Studio 2017 version 15.9 (includes 15.0 – 15.8) · Spoofing

Affects Microsoft Visual Studio 2017 version 15.9 (includes 15.0 – 15.8)Source CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.4% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NuGetmicrosoft.visualstudiopkg:nuget/microsoft.visualstudioOther threatsAffected
  • =15.9.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches in the provided information, European organizations should implement several targeted mitigations: 1) Upgrade to a newer, supported version of Microsoft Visual Studio where this vulnerability is addressed, or apply any available security updates from Microsoft promptly. 2) Restrict network access to development environments to trusted internal networks and use VPNs with strong authentication to reduce exposure to remote attacks. 3) Employ application whitelisting and code signing policies to ensure only verified components are loaded within the IDE. 4) Conduct regular code reviews and use static and dynamic analysis tools to detect anomalous or spoofed code artifacts. 5) Educate developers about the risks of spoofing attacks and encourage vigilance regarding unexpected IDE behaviors or prompts. 6) Monitor development environment logs for unusual activities that could indicate exploitation attempts. 7) Implement strict access controls and multi-factor authentication for development resources to limit unauthorized access.

Description

.NET Spoofing Vulnerability

References

Community reviews

Loading reviews…