Microsoft Visual Studio heap buffer overflow RCE

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

Visual Studio is a development tool used by programmers to build and test applications. A heap buffer overflow vulnerability allows an attacker to execute malicious code on a developer's machine over the network, potentially compromising all projects and data the developer has access to. The vulnerability requires user interaction to exploit.

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 an unauthorized attacker to execute code remotely with network attack vector. The attack requires user interaction and does not require prior authentication or privilege escalation. Successful exploitation grants the attacker arbitrary code execution on the affected system.

Affected products

  • Microsoft Visual Studio

Timeline

  • 2026-11-10: disclosed
  • 2026-11-10: advisory

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