DEV Community

CVE Reports
CVE Reports

Posted on • Originally published at cvereports.com

CVE-2026-32177: CVE-2026-32177: Heap-Based Buffer Overflow in .NET Core and Visual Studio

#security #cve #cybersecurity

CVE-2026-32177: Heap-Based Buffer Overflow in .NET Core and Visual Studio

Vulnerability ID: CVE-2026-32177
CVSS Score: 7.3
Published: 2026-05-12

CVE-2026-32177 is a high-severity heap-based buffer overflow affecting multiple versions of Microsoft .NET and Visual Studio. Triggered by insufficient input validation during file processing, the vulnerability permits local privilege escalation when a user opens a specially crafted file.

TL;DR

A heap-based buffer overflow in the .NET runtime allows local privilege escalation when users open maliciously crafted files in vulnerable host applications like Visual Studio.

Technical Details

  • CWE ID: CWE-122
  • Attack Vector: Local (AV:L)
  • CVSS v3.1 Score: 7.3 (High)
  • EPSS Probability: 0.10%
  • Primary Impact: Local Elevation of Privilege
  • Exploit Status: Unexploited / No PoC
  • CISA KEV: Not Listed

Affected Systems

  • .NET 10.0
  • .NET 9.0
  • .NET 8.0
  • Microsoft .NET Framework 3.5
  • Microsoft .NET Framework 4.7.2
  • Microsoft .NET Framework 4.8
  • Microsoft .NET Framework 4.8.1
  • Microsoft Visual Studio 2022
  • Microsoft Visual Studio 2026
  • .NET 10.0: 10.0.0 to 10.0.7 (Fixed in: 10.0.8)
  • .NET 9.0: 9.0.0 to 9.0.15 (Fixed in: 9.0.16)
  • .NET 8.0: 8.0.0 to 8.0.26 (Fixed in: 8.0.27)
  • Microsoft .NET Framework 3.5, 4.7.2, 4.8, 4.8.1: All prior to patch (Fixed in: 4.8.9334.0 / 4.8.4802.0)
  • Microsoft Visual Studio 2022: 17.12.0 to 17.12.19, 17.14.0 to 17.14.30 (Fixed in: 17.12.20 / 17.14.31)
  • Microsoft Visual Studio 2026: 18.5.0 to 18.5.2 (Fixed in: 18.5.3)

Mitigation Strategies

  • Apply Microsoft May 2026 Patch Tuesday security updates across all affected .NET environments.
  • Enforce the principle of least privilege to prevent users from running development tools or applications with administrative rights.
  • Implement file screening and security controls to block suspicious or untrusted files.

Remediation Steps:

  1. Inventory all systems running .NET 8.0, 9.0, 10.0, and .NET Framework.
  2. Identify installations of Visual Studio 2022 and 2026.
  3. Deploy the specific fixed versions listed in the MSRC advisory (e.g., .NET 10.0.8, VS 2026 18.5.3).
  4. Verify the patch installation by checking assembly file versions.

References

Read the full report for CVE-2026-32177 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)