Improper certificate validation flaw in Visual Studio 2017
CVE-2026-118147 – Visual Studio ·
In this episode
The facts
- CVE-2026-118147 is a flaw in Microsoft Visual Studio 2017 version 15.9.
- CVE-2026-118147 is classed as improper certificate validation (CWE-295).
- According to its CVSS rating, CVE-2026-118147 can be exploited remotely over the network, without any credentials and without user interaction.
- CVE-2026-118147 is rated 7.4 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CVE-2026-118147 is a flaw in Microsoft Visual Studio 2017 version 15.9. It is classed as improper certificate validation, CWE-295, and carries a CVSS score of 7.4. The rating says it can be exploited remotely over the network, without any credentials and without user interaction.
Jordan Pike AI host
If your organization still runs Visual Studio 2017, especially on workstations that can reach the internet, you need to pay attention. The board will want to know the exposure, and your help desk will see a flood of tickets if the issue is abused. Because the vulnerability can be triggered over the network, any endpoint that can talk to external servers is in scope. Make sure your asset inventory flags every machine still on version 15.9. What’s the one thing you should do on Monday?
Maya Okafor AI analyst
Improper certificate validation (CWE-295) means the software accepts a TLS certificate without fully verifying its authenticity. The CVSS details show an attacker can trigger the flaw remotely, without credentials or user interaction. This class of bug often appears when developers disable checks for convenience, which can slip into released tools. A proper fix requires Microsoft to enforce full validation in the product code. Organizations should consider moving to a newer Visual Studio version and review any custom components that might bypass certificate checks. Auditing the build environment for such shortcuts is also prudent.
Maya Okafor AI analyst
Looks like Visual Studio decided to play ‘trust the stranger’—bold move.
Dex Moreno AI analyst
From an attacker’s perspective, the ability to exploit the flaw remotely without credentials or user action is attractive. By presenting a server that Visual Studio contacts, an adversary could cause the tool to accept malicious code, giving the attacker execution on the developer’s workstation. That foothold can then be used to embed backdoors into compiled binaries, potentially affecting any downstream customers who receive those binaries. Because the tool often runs on machines with broad network access, the impact can spread beyond the initial host.
Dex Moreno AI analyst
If a patch becomes available, applying it promptly is the quickest mitigation. In the meantime, organisations can restrict outbound connections from machines running Visual Studio to only trusted internal servers, reducing the chance of a malicious response being processed. Network segmentation that isolates development machines from the internet also helps limit exposure.
Sam Kowalski AI analyst
Start by reviewing network connection logs from any system running Visual Studio 2017 for unexpected outbound connections, especially to unknown internet hosts. Correlate those entries with process creation events to spot unusual activity. Check Windows Event logs for any new binaries appearing in the Visual Studio installation directory. If a suspicious connection or file is found, isolate the host, capture its memory, and preserve any related build artifacts for later investigation. Early containment prevents the workstation from being used as a launch point.
Rina Takahashi AI analyst
The public data does not attribute the vulnerability to any specific threat group. Keep CVE-2026-118147 on your monitoring list and watch for any activity that matches the described remote, unauthenticated exploitation pattern. Given the ease of remote access, the flaw is likely to attract both opportunistic actors and more focused groups.
Jordan Pike AI host
Well, that’s a classic case of ‘trust issues’ in code.
Jordan Pike AI host
Bottom line: when a patch is released, apply it promptly, segment development machines from the internet, and monitor for unexpected outbound traffic from Visual Studio hosts. Record the patch status in your configuration management database and report compliance to your auditors. That gives you a concrete Monday action plan.