Vulnerability Database · NuGet · Package report

Microsoft.Diagnostics.Runtime: vulnerability history, versions and safety

Microsoft.Diagnostics.Runtime is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on Microsoft.Diagnostics.Runtime 4.2.751201 i

Updated on 23 Oct 2026

Good news: 4.2.751201, the version you would install today, has no known vulnerabilities.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 4.2.751201 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,168 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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.Diagnostics.Runtime, 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
4.2.751201 12 Oct 2026 none MIT — Details →
4.2.750101 07 Oct 2026 none MIT — Details →
4.1.745802 09 Sep 2026 none MIT — Details →
4.0.732401 25 Jun 2026 none MIT — Details →
4.0.732101 22 Jun 2026 none MIT — Details →
4.0.726401 14 May 2026 none MIT — Details →
4.0.726301 13 May 2026 none MIT — Details →
4.0.726102 12 May 2026 none MIT — Details →
4.0.725402 04 May 2026 none MIT — Details →
4.0.725202 04 May 2026 none MIT — Details →
4.0.723004 30 Apr 2026 none MIT — Details →
4.0.722401 24 Apr 2026 none MIT — Details →
4.0.0-beta.26203.1 06 Apr 2026 none MIT — Details →
4.0.0-beta.26202.1 02 Apr 2026 none MIT — Details →
4.0.0-beta.24360.3 11 Jul 2024 none MIT — Details →
4.0.0-beta.24360.2 10 Jul 2024 none MIT — Details →
4.0.0-beta.24320.3 20 Jun 2024 none MIT — Details →
4.0.0-beta.24314.3 14 Jun 2024 none MIT — Details →
3.1.512801 29 Feb 2024 none MIT — Details →
3.1.506101 01 Feb 2024 none MIT — Details →
3.1.456101 13 Nov 2023 none MIT — Details →
3.1.456003 11 Nov 2023 none MIT — Details →
3.1.455904 10 Nov 2023 none MIT — Details →
3.0.442202 22 Aug 2023 none MIT — Details →
3.0.0-beta.23214.4 17 Apr 2023 none MIT — Details →
3.0.0-beta.23177.1 28 Mar 2023 none MIT — Details →
3.0.0-beta.23165.1 16 Mar 2023 none MIT — Details →
2.4.416101 12 Mar 2023 none MIT — Details →
3.0.0-beta.23159.4 09 Mar 2023 none MIT — Details →
3.0.0-beta.23158.2 09 Mar 2023 none MIT — Details →
3.0.0-beta.23156.1 06 Mar 2023 none MIT — Details →
2.3.405304 05 Jan 2023 none MIT — Details →
2.2.343001 31 Oct 2022 none MIT — Details →
2.2.332302 23 Jun 2022 none MIT — Details →
2.2.332001 20 Jun 2022 none MIT — Details →
2.1.327703 27 May 2022 none MIT — Details →
2.0.226801 19 May 2021 none MIT — Details →
2.0.226401 14 May 2021 none MIT — Details →
2.0.222201 22 Apr 2021 none MIT — Details →
2.0.221201 14 Apr 2021 none MIT — Details →
2.0.217201 22 Mar 2021 none MIT — Details →
2.0.161401 14 Dec 2020 none MIT — Details →
2.0.156101 18 Nov 2020 none MIT — Details →
2.0.151903 19 Oct 2020 none MIT — Details →
2.0.145301 04 Sep 2020 none MIT — Details →
2.0.142701 28 Aug 2020 none MIT — Details →
2.0.142501 25 Aug 2020 none MIT — Details →
2.0.142103 21 Aug 2020 none MIT — Details →
1.1.142101 21 Aug 2020 none MIT — Details →
2.0.141902 19 Aug 2020 none MIT — Details →
2.0.137201 22 Jul 2020 none MIT — Details →
1.1.132302 23 Jun 2020 none MIT — Details →
2.0.130507 06 Jun 2020 none MIT — Details →
2.0.0-rc.20303.6 04 Jun 2020 none MIT — Details →
1.1.127808 29 May 2020 none MIT — Details →
2.0.0-rc.20278.6 28 May 2020 none MIT — Details →
2.0.0-beta.20276.4 27 May 2020 none MIT — Details →
2.0.0-beta.20273.1 23 May 2020 none MIT — Details →
2.0.0-beta.20272.2 22 May 2020 none MIT — Details →
2.0.0-beta.20272.1 22 May 2020 none MIT — Details →
2.0.0-beta.20268.2 18 May 2020 none MIT — Details →
1.1.126102 17 May 2020 none MIT — Details →
2.0.0-beta.20230.2 30 Apr 2020 none MIT — Details →
2.0.0-beta.20230.1 30 Apr 2020 none MIT — Details →
2.0.0-beta.20229.3 30 Apr 2020 none MIT — Details →
2.0.0-beta.20223.2 23 Apr 2020 none MIT — Details →
2.0.0-beta.20222.8 23 Apr 2020 none MIT — Details →
2.0.0-beta.20222.7 23 Apr 2020 none MIT — Details →
2.0.0-beta.20222.5 22 Apr 2020 none MIT — Details →
2.0.0-beta.20220.3 20 Apr 2020 none MIT — Details →
1.1.122004 20 Apr 2020 none MIT — Details →
2.0.0-beta.20213.1 13 Apr 2020 none MIT — Details →
2.0.0-beta.20174.2 24 Mar 2020 none MIT — Details →
1.1.116301 13 Mar 2020 none MIT — Details →
2.0.0-beta.20072.5 23 Jan 2020 none MIT — Details →
1.1.61812 19 Dec 2019 none MIT — Details →
2.0.0-beta.19618.7 19 Dec 2019 none MIT — Details →
2.0.0-beta.19612.8 12 Dec 2019 none MIT — Details →
1.1.57604 26 Nov 2019 none MIT — Details →
1.1.57004 20 Nov 2019 none MIT — Details →
1.1.46104 11 Sep 2019 none non-standard — Details →
1.1.37504 25 Jul 2019 none non-standard — Details →
1.1.35902 09 Jul 2019 none non-standard — Details →
1.1.35504 05 Jul 2019 none non-standard — Details →
1.0.5 19 Mar 2019 none non-standard — Details →
1.0.3 13 Feb 2019 none non-standard — Details →
1.0.2 17 Dec 2018 none non-standard — Details →
1.0.0 22 Nov 2018 none non-standard — Details →
0.9.180305.1 06 Mar 2018 none non-standard — Details →
0.9.170809.3 09 Aug 2017 none non-standard — Details →
0.9.170626.1 26 Jun 2017 none non-standard — Details →
0.8.31-beta 15 Oct 2015 none non-standard — Details →
0.8.30-beta 16 Sep 2015 none non-standard — Details →
0.8.24-aamain00309 02 Dec 2014 none non-standard — Details →
0.8.27-beta 30 Sep 2014 none non-standard — Details →
0.8.26-beta 14 Aug 2014 none non-standard — Details →
0.8.25-beta 12 Mar 2014 none non-standard — Details →
0.7.1-beta 03 May 2013 none non-standard — Details →
0.8.24 — none non-standard — Details →
1.0.1-dev — none non-standard — Details →
1.1.61810 — none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.Diagnostics.Runtime

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.Diagnostics.Runtime

Is Microsoft.Diagnostics.Runtime safe to use?

Vulert has no vulnerabilities on record for Microsoft.Diagnostics.Runtime in NuGet at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is Microsoft.Diagnostics.Runtime's Vulert package health score?

Vulert scores Microsoft.Diagnostics.Runtime 82/100, which reads as in good shape. 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.Diagnostics.Runtime affected?

No. 4.2.751201, 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.Diagnostics.Runtime should I use?

4.2.751201 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.Diagnostics.Runtime have?

0 vulnerabilities are recorded for Microsoft.Diagnostics.Runtime in the NuGet ecosystem: 0 critical, 0 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.Diagnostics.Runtime vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.Diagnostics.Runtime in the last 12 months. 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.Diagnostics.Runtime 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.Diagnostics.Runtime for upcoming vulnerabilities?

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