CVE-2026-69522: .NET and Visual Studio Remote Code Execution Vulnerability

Published Sep 8, 2026
·
Updated

.NET and Visual Studio Remote Code Execution Vulnerability

Other sources

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

— Microsoft

Affected Software

22 affected componentsFixes available
nuget/Microsoft.DiaSymReader.Native>=17.10.0-beta1.24272.1<=18.9.0-beta1.26405.1
18.9.0-beta1.26405.2
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0
Microsoft .NET Framework=3.5, =4.6.2, =4.7, =4.7.1, =4.7.2
2.0.50727.9070 & 3.0.30729.9068 & 4.7.4145.0
Microsoft Visual Studio 2026=18.9
18.9.3
Microsoft .NET 11.0 installed on Windows<11.0 RC1
11.0 RC1
Microsoft .NET Framework=3.5, =4.7.2
2.0.50727.9070 & 3.0.30729.9068 & 4.7.4145.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0
Microsoft .NET Framework=3.5, =4.8.1
2.0.50727.9183 & 3.0.30729.9169 & 4.8.9346.0
Microsoft .NET Framework=4.8.1
4.8.9347.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4145.0
Microsoft .NET Framework=3.5, =4.6.2, =4.7, =4.7.1, =4.7.2
2.0.50727.8984 & 3.0.30729.8980 & 4.7.4145.0
Microsoft .NET Framework=4.6.2, =4.7, =4.7.1, =4.7.2
4.7.4145.0
Microsoft .NET Framework=4.8
4.8.4806.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9183 & 3.0.30729.9169 & 4.8.4806.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9183 & 3.0.30729.9169 & 4.8.4806.0
Microsoft .NET Framework=4.8
4.8.4806.0
Microsoft .NET Framework=3.5, =4.8
2.0.50727.9070 & 3.0.30729.9068 & 4.8.4806.0
Microsoft Visual Studio 2022=17.14
17.14.40
Microsoft .NET Framework=4.8
4.8.4806.0
Microsoft .NET 8.0 installed on Windows<8.0.31
8.0.31
Microsoft .NET 10.0 installed on Windows<10.0.12
10.0.12
Microsoft .NET 9.0 installed on Windows<9.0.20
9.0.20

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade nuget/Microsoft.DiaSymReader.Native to a version that resolves this vulnerability.

    Fixed in 18.9.0-beta1.26405.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0Patch KB5126052
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9070 & 3.0.30729.9068 & 4.7.4145.0Patch KB5126043
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.9.3
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 11.0 RC1
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0Patch KB5126424
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9346.0Patch KB5126421
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.9347.0Patch KB5126053
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4145.0Patch KB5126045
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.9347.0Patch KB5126422
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8984 & 3.0.30729.8980 & 4.7.4145.0Patch KB5123099
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4145.0Patch KB5126044
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4806.0Patch KB5126047
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.4806.0Patch KB5126046
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9183 & 3.0.30729.9169 & 4.8.4806.0Patch KB5126050
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4806.0Patch KB5126051
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9070 & 3.0.30729.9068 & 4.8.4806.0Patch KB5126048
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.14.40
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4806.0Patch KB5126049
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.31Patch KB5126104
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.12Patch KB5126106
  22. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.0.20Patch KB5126105
  23. Upgrade

    Upgrade Microsoft.DiaSymReader.Native to a version that resolves this vulnerability.

    Fixed in 18.9.0-beta1.26405.2
  24. Operational

    After updating the runtime, SDK, Visual Studio, or the Microsoft.DiaSymReader.Native package to the fixed version, restart affected apps for the update to take effect.

Event History

Sep 8, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·05:10 PM
Data Sourced
via MITRE·05:10 PM
DescriptionSeverity
Data Sourced
via NVD·06:19 PM
DescriptionSeverityWeakness
Sep 9, 2026
Advisory Published
via GitHub·04:04 PM
Data Sourced
via GitHub·04:04 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Does exploitation require an authenticated account or elevated privileges?

No. The vector indicates network exploitation with low attack complexity and no privileges required, although user interaction is required.

2

What is the potential impact if exploitation succeeds?

Successful exploitation can result in remote code execution. The supplied scoring data indicates high impact to confidentiality, integrity, and availability.

3

Which listed products should be included in exposure assessment?

Assess Microsoft Visual Studio 2022 and Visual Studio 2026, plus Windows installations of Microsoft .NET Framework and .NET 8.0, 9.0, 10.0, and 11.0.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203