Microsoft Visual Studio heap-based buffer overflow

Severity: high · CVSS 8.8 · Published 2026-11-10

Visual Studio, a development platform used by programmers to write and test software, contains a heap-based buffer overflow vulnerability that could allow an attacker to execute arbitrary code remotely over a network. An attacker can exploit this with user interaction to achieve complete compromise of the affected system, including data theft, system modification, and denial of service.

Technologies: Microsoft Visual Studio, Microsoft.NetCore.App.Runtime.win-x86 (NuGet). Vendors: Microsoft, NuGet.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
High severity, with a CVSS score of 8.8, published 10 November 2026.
Which products and versions are affected?
Microsoft.NetCore.App.Runtime.win-x86 (NuGet) >= 8.0.0, < 8.0.34, ECOSYSTEM:introduced=8.0.0.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network.
Am I affected?
Check whether you run Microsoft Visual Studio or Microsoft.NetCore.App.Runtime.win-x86 (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A heap-based buffer overflow in Visual Studio allows remote code execution when user interaction occurs. The attack vector is network-based with no privilege requirement but requires user interaction. This is a CWE-122 buffer overflow that permits arbitrary code execution with full system impact.

Affected products

  • Microsoft Visual Studio

Timeline

  • 2026-11-10: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.