VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Microsoft.NETCore.App: vulnerability history, versions and safety

Microsoft.NETCore.App is a package in the NuGet ecosystem. Vulert records 8 vulnerabilities for it across 42 releases, from May 2022 to Oct 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H4 M4
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.

See all Microsoft.NETCore.App vulnerabilities

Vulert verdict on Microsoft.NETCore.App 2.2.8 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 2.2.8 — unaffected i
  • Vulnerabilities on record 8 over 1 year · 0 in the last year i
  • Latest disclosure 20 Oct 2022 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Last release 83 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.NETCore.App, 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
2.1.30 19 Aug 2021 none non-standard — Details →
2.1.29 10 Aug 2021 none non-standard — Details →
2.1.28 11 May 2021 M1 non-standard Yes Details →
2.1.27 06 Apr 2021 M1 non-standard Yes Details →
2.1.26 09 Mar 2021 M1 non-standard Yes Details →
2.1.25 09 Feb 2021 M1 non-standard Yes Details →
2.1.24 12 Jan 2021 M2 non-standard Yes Details →
2.1.23 13 Oct 2020 M2 non-standard Yes Details →
2.1.22 08 Sep 2020 M2 non-standard Yes Details →
2.1.21 11 Aug 2020 M2 non-standard Yes Details →
2.1.20 14 Jul 2020 M2 non-standard Yes Details →
2.1.19 09 Jun 2020 H1 M2 non-standard Yes Details →
2.1.18 12 May 2020 H1 M2 non-standard Yes Details →
2.1.17 24 Mar 2020 H2 M2 non-standard Yes Details →
2.1.16 18 Feb 2020 H2 M2 non-standard Yes Details →
2.1.15 14 Jan 2020 H2 M2 non-standard Yes Details →
2.1.14 18 Nov 2019 H2 M2 non-standard Yes Details →
2.2.8 18 Nov 2019 none non-standard — Details →
2.1.13 10 Sep 2019 H2 M2 non-standard Yes Details →
2.2.7 10 Sep 2019 none non-standard — Details →
2.1.12 09 Jul 2019 H2 M2 non-standard Yes Details →
2.2.6 09 Jul 2019 none non-standard — Details →
2.1.11 14 May 2019 H2 M2 non-standard Yes Details →
1.1.13 14 May 2019 none non-standard — Details →
2.2.5 14 May 2019 none non-standard — Details →
1.0.16 14 May 2019 none non-standard — Details →
2.1.10 09 Apr 2019 H2 M2 non-standard Yes Details →
2.2.4 09 Apr 2019 none non-standard — Details →
2.2.3 12 Mar 2019 none non-standard — Details →
1.0.15 11 Mar 2019 none non-standard — Details →
2.1.9 11 Mar 2019 H2 M2 non-standard Yes Details →
1.1.12 11 Mar 2019 none non-standard — Details →
1.1.11 12 Feb 2019 none non-standard — Details →
1.0.14 12 Feb 2019 none non-standard — Details →
2.2.2 12 Feb 2019 none non-standard — Details →
2.1.8 12 Feb 2019 H2 M2 non-standard Yes Details →
2.2.1 08 Jan 2019 M1 non-standard Yes Details →
2.1.7 08 Jan 2019 H2 M2 non-standard Yes Details →
2.2.0 03 Dec 2018 M1 non-standard Yes Details →
2.1.6 13 Nov 2018 H3 M3 non-standard Yes Details →
2.2.0-preview3-27014-02 17 Oct 2018 M1 non-standard Yes Details →
1.1.10 09 Oct 2018 none non-standard — Details →
1.0.13 09 Oct 2018 none non-standard — Details →
2.1.5 01 Oct 2018 H3 M3 non-standard Yes Details →
2.2.0-preview2-26905-02 12 Sep 2018 M1 non-standard Yes Details →
2.1.4 11 Sep 2018 H3 M3 non-standard Yes Details →
2.2.0-preview-26820-02 22 Aug 2018 M1 non-standard Yes Details →
2.1.3 21 Aug 2018 H3 M3 non-standard Yes Details →
2.0.9 10 Jul 2018 none non-standard — Details →
1.1.9 10 Jul 2018 none non-standard — Details →
1.0.12 10 Jul 2018 none non-standard — Details →
2.1.2 10 Jul 2018 H3 M3 non-standard Yes Details →
2.1.1 18 Jun 2018 H3 M3 non-standard Yes Details →
2.1.0 29 May 2018 H3 M3 non-standard Yes Details →
2.1.0-rc1 06 May 2018 none non-standard — Details →
2.0.7 16 Apr 2018 none non-standard — Details →
1.1.8 16 Apr 2018 none non-standard — Details →
1.0.11 16 Apr 2018 none non-standard — Details →
2.1.0-preview2-26406-04 10 Apr 2018 H3 M3 non-standard Yes Details →
2.0.6 13 Mar 2018 none non-standard — Details →
1.1.7 13 Mar 2018 none non-standard — Details →
1.0.10 13 Mar 2018 none non-standard — Details →
2.1.0-preview1-26216-03 26 Feb 2018 H3 M3 non-standard Yes Details →
2.0.5 09 Jan 2018 none non-standard — Details →
1.1.6 09 Jan 2018 none non-standard — Details →
1.0.9 09 Jan 2018 none non-standard — Details →
2.0.4 12 Dec 2017 none non-standard — Details →
2.0.3 14 Nov 2017 none non-standard — Details →
1.1.5 14 Nov 2017 none non-standard — Details →
1.0.8 14 Nov 2017 none non-standard — Details →
1.1.4 20 Sep 2017 none non-standard — Details →
1.0.7 20 Sep 2017 none non-standard — Details →
2.0.0 11 Aug 2017 none non-standard — Details →
2.0.0-preview2-25407-01 27 Jun 2017 none non-standard — Details →
2.0.0-preview1-002111-00 09 May 2017 none non-standard — Details →
1.1.2 09 May 2017 none non-standard — Details →
1.0.5 09 May 2017 H1 non-standard Yes Details →
1.1.1 06 Mar 2017 none non-standard — Details →
1.0.4 06 Mar 2017 H1 non-standard Yes Details →
1.0.3 13 Dec 2016 H1 non-standard Yes Details →
1.1.0 16 Nov 2016 none non-standard — Details →
1.1.0-preview1-001100-00 24 Oct 2016 none non-standard — Details →
1.0.1 30 Aug 2016 H1 non-standard Yes Details →
1.0.0 27 Jun 2016 H1 non-standard Yes Details →
1.0.0-rc2-3002702 16 May 2016 none non-standard — Details →
1.0.5-servicing-004880-00 — H1 non-standard Yes Details →
3.0.0-preview-27122-01 — none non-standard — Details →
3.0.0-preview-27324-5 — none non-standard — Details →
3.0.0-preview3-27503-5 — none non-standard — Details →
3.0.0-preview4-27615-11 — none non-standard — Details →
3.0.0-preview5-27626-15 — none non-standard — Details →
3.0.0-preview6-27804-01 — none non-standard — Details →
3.0.0-preview7-27912-14 — none non-standard — Details →
3.0.0-preview8-28405-07 — none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 8

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

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.NETCore.App

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-1147: .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability 7.8 high 2.1.20 24 May 2022
CVE-2019-0545: Exposure of Sensitive Information in System.Net.Http 7.5 high 2.1.7 14 May 2022
CVE-2020-1108: .NET Core & .NET Framework Denial of Service Vulnerability 7.5 high 2.1.18 24 May 2022
CVE-2017-8585: Improper Input Validation in Microsoft.NETCore.App 7.5 high 1.0.7 17 May 2022
CVE-2018-8416: Tampering vulnerability in .NET Core 6.5 medium 2.1.7 13 May 2022

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.NETCore.App

Is Microsoft.NETCore.App safe to use?

Vulert records 8 vulnerabilities for Microsoft.NETCore.App in NuGet: 0 critical, 4 high, 4 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.NETCore.App's Vulert package health score?

Vulert scores Microsoft.NETCore.App 73/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.NETCore.App affected?

No. 2.2.8, 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.NETCore.App should I use?

2.1.30 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.NETCore.App have?

8 vulnerabilities are recorded for Microsoft.NETCore.App in the NuGet ecosystem: 0 critical, 4 high, 4 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.NETCore.App vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.NETCore.App in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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.NETCore.App 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.NETCore.App for upcoming vulnerabilities?

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