Search threats, CVEs… ⌘K
Back to vendor advisories
Microsoft Security Response CenterCVE-2026-69522

.NET and Visual Studio Remote Code Execution Vulnerability

HighVendor CVSS 8.8 / 10 1 CVE Published Sep 8, 2026 at 7:00 AM UTC
Get alerts for NET 10.0 runtime installed on Windows

Summary

Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.

Products covered

  • .NET 10.0 runtime installed on Windows

  • .NET 8.0 runtime installed on Windows

  • .NET 9.0 runtime installed on Windows

  • Microsoft Visual Studio 2022 version 17.14

  • Microsoft .NET Framework 4.8 on Windows Server 2012

  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems

  • Microsoft .NET Framework 4.8 on Windows Server 2012 R2

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems

Show 39 more products

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for 32-bit Systems

  • Microsoft .NET Framework 4.8 on Windows Server 2016

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 22H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019

  • Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 Version 1607 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016

  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012

  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2

  • Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1 for x64-based Systems

  • Microsoft .NET Framework 4.8.1 on Windows 11 Version 26H1 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 21H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 Version 22H2 for 32-bit Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 25H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 25H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 23H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 24H2 for x64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025

  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 Version 24H2 for ARM64-based Systems

  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems

  • Microsoft Visual Studio 2026 version 18.9

  • .NET 11.0 runtime installed on Windows

  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for ARM64-based Systems

Remediation

Release Notes Install KB5126106. Install KB5126104. Install KB5126105. Install KB5126049. Install KB5126047. Install KB5126051. Install KB5126048. Install KB5126050. Install KB5126046. Install KB5126043. Install KB5123099. Install KB5126044. Install KB5126045. Install KB5126053. Install KB5126422. Install KB5126421. Install KB5126052. Install KB5126424.

Vendor-listed fixes

  • 10.0.12

  • 8.0.31

  • 9.0.20

  • 17.14.40

  • 4.8.4806.0

  • 2.0.50727.9070 & 3.0.30729.9068 & 4.8.4806.0

  • 2.0.50727.9183 & 3.0.30729.9169 & 4.8.4806.0

  • 2.0.50727.9070 & 3.0.30729.9068 & 4.7.4145.0

Show 7 more fixes

  • 2.0.50727.8984 & 3.0.30729.8980 & 4.7.4145.0

  • 4.7.4145.0

  • 4.8.9347.0

  • 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0

  • 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9346.0

  • 18.9.3

  • 11.0 RC1

CVEs in this advisory 1

CVE-2026-69522
Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • Added affected products: .NET 8.0 runtime installed on Windows, .NET 9.0 runtime installed on Windows, .NET 10.0 runtime installed on Windows, .NET 11.0 runtime installed on Windows.
    • Removed affected products: .NET 8.0 installed on Windows, .NET 9.0 installed on Windows, .NET 10.0 installed on Windows, .NET 11.0 installed on Windows.
    • Added affected products: Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019.
    • Removed affected products: Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019.
    • The vendor changed its remediation guidance.
    • The vendor changed the advisory's last-updated date.
    • The vendor changed its remediation guidance.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.

Keep investigating
See every advisory from this vendor