Live › vulnerability › CVE-2026-69522
Microsoft.DiaSymReader.Native, a NuGet package used by .NET and Visual Studio to read PDB debug files, has a heap buffer overflow when processing PDB files. An attacker who gets a crafted PDB file processed on a Windows machine can run code there.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-04 04:12 UTC, 0h before NVD. All times on this page are UTC.
Any .NET project on Windows that references Microsoft.DiaSymReader.Native within the affected ranges, and machines running the affected .NET or Visual Studio builds, are exposed. The advisory says the flaw is triggered when PDB files are processed, so the risk depends on whether a project or tool reads PDB files from untrusted sources; the advisory gives no further detail.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Microsoft.DiaSymReader.Native | nuget | >= 17.10.0-beta1.24272.1, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 |
Microsoft.DiaSymReader.Native and check whether the resolved version is between 17.10.0-beta1.24272.1 and 18.9.0-beta1.26405.1 (.NET 10, 9 and 8 ranges differ, see the advisory)Upgrade to 18.9.0-beta1.26405.2
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Microsoft is releasing this security advisory to provide information about a vulnerability in Microsoft.DiaSymReader.Native. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An out of bounds write can occur when processing PDB files.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/439
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HThe vulnerability affects any Microsoft .NET project if it uses any of affected package versions listed below
Supported .NET Framework versions listed in the Microsoft Security Update Guide are also affected. Install the September 2026 .NET Framework security update applicable to a project's Windows version.
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.DiaSymReader.Native | >= 17.10.0-beta1.24272.1, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.DiaSymReader.Native | >= 17.12.0-beta1.24603.5, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.DiaSymReader.Native | >= 17.12.0-beta1.24603.5, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 |
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.DiaSymReader.Native | >= 17.12.0-beta1.24603.5, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 |
If using a package listed in affected packages, a project is exposed to the vulnerability.
Once users have installed the updated runtime, SDK, Visual Studio, or package, they should restart their apps for the update to take effect.
If users have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Users can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. Users can ask questions in the linked discussion issue.
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
41ae55e9310ff27fa6f26af4727e5590
V1.0 (09/08/2026): Advisory published.
This page as .md · .json · in your agent: get_signal("CVE-2026-69522")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.