VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Microsoft.DiaSymReader.Native: vulnerability history, versions and safety

Microsoft.DiaSymReader.Native is a package in the NuGet ecosystem. Vulert records 6 vulnerabilities for it across 3 releases, first recorded in Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 09 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all Microsoft.DiaSymReader.Native vulnerabilities

Vulert verdict on Microsoft.DiaSymReader.Native 1.7.0 i

Updated on 23 Oct 2026

Good news: 1.7.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 53/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 1.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.7.0 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 6 in the last year i
  • Latest disclosure 09 Sep 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Last release 106 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for Microsoft.DiaSymReader.Native, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
18.8.4-beta1.26356.2 08 Jul 2026 H6 non-standard Yes Details →
17.12.0-beta1.24603.5 15 Jan 2025 H6 non-standard Yes Details →
17.10.0-beta1.24272.1 24 May 2024 H6 non-standard Yes Details →
17.8.7-beta1.24113.1 16 Feb 2024 none non-standard — Details →
17.8.0-beta1.23475.2 26 Sep 2023 none non-standard — Details →
16.11.29-beta1.23404.4 12 Sep 2023 none non-standard — Details →
16.11.27-beta1.23180.1 13 Jun 2023 none non-standard — Details →
16.11.23-beta1.23063.1 15 Feb 2023 none non-standard — Details →
15.9.52-beta1.23070.1 15 Feb 2023 none non-standard — Details →
17.0.0-beta1.21524.1 25 Oct 2021 none non-standard — Details →
16.9.0-beta1.21055.5 06 Jan 2021 none non-standard — Details →
1.7.0 05 Dec 2017 none non-standard — Details →
1.5.0 09 Mar 2017 none non-standard — Details →
1.4.2 10 Feb 2017 none non-standard — Details →
1.4.1 02 Feb 2017 none non-standard — Details →
1.5.0-beta2-24728 07 Dec 2016 none non-standard — Details →
1.5.0-beta1 01 Aug 2016 none non-standard — Details →
1.4.0 21 Jun 2016 none non-standard — Details →
1.4.0-rc2 08 Jun 2016 none non-standard — Details →
1.4.0-rc 19 May 2016 none non-standard — Details →
1.3.3 04 Nov 2015 none non-standard — Details →
1.2.0-rc 08 Oct 2015 none non-standard — Details →
1.1.0-alpha2 18 Aug 2015 none non-standard — Details →
1.1.0-alpha1 26 Jul 2015 none non-standard — Details →
1.0.0-rc2 — none non-standard — Details →
1.3.0 — none non-standard — Details →
1.3.1 — none non-standard — Details →
1.3.2 — none non-standard — Details →
15.9.52-beta1.23060.8 — none non-standard — Details →

All 29 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.DiaSymReader.Native

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Remote Code Execution Vulnerability in Microsoft.DiaSymReader.Native Package 8.8 high 18.9.0-beta1.26405.2 08 Sep 2026
CVE-2026-69522: Microsoft.DiaSymReader.Native Remote Code Execution Vulnerability 8.8 high 18.9.0-beta1.26405.2 09 Sep 2026
Critical Remote Code Execution Vulnerability in Microsoft.DiaSymReader.Native Package 8.8 high 18.9.0-beta1.26405.2 08 Sep 2026
CVE-2026-69439: Microsoft.DiaSymReader.Native Elevation of Privilege Vulnerability 8.8 high 18.9.0-beta1.26405.2 09 Sep 2026
CVE-2026-71328: Microsoft.DiaSymReader.Native Remote Code Execution Vulnerability 8.8 high 18.9.0-beta1.26405.2 09 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About Microsoft.DiaSymReader.Native

Is Microsoft.DiaSymReader.Native safe to use?

Vulert records 6 vulnerabilities for Microsoft.DiaSymReader.Native in NuGet: 0 critical, 6 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is Microsoft.DiaSymReader.Native's Vulert package health score?

Vulert scores Microsoft.DiaSymReader.Native 53/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of Microsoft.DiaSymReader.Native affected?

No. 1.7.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of Microsoft.DiaSymReader.Native should I use?

1.7.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does Microsoft.DiaSymReader.Native have?

6 vulnerabilities are recorded for Microsoft.DiaSymReader.Native in the NuGet ecosystem: 0 critical, 6 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new Microsoft.DiaSymReader.Native vulnerabilities disclosed?

6 vulnerabilities were recorded for Microsoft.DiaSymReader.Native in the last 12 months, and the oldest entry in this database dates to 08 Sep 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of Microsoft.DiaSymReader.Native are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor Microsoft.DiaSymReader.Native for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the Microsoft.DiaSymReader.Native version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.