VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Microsoft.Build.NuGetSdkResolver: vulnerability history, versions and safety

Microsoft.Build.NuGetSdkResolver is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Jun 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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.Build.NuGetSdkResolver vulnerabilities

Vulert verdict on Microsoft.Build.NuGetSdkResolver 5.11.0-rc.10 i

Updated on 23 Oct 2026

Careful: 5.11.0-rc.10 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Some issues to review
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.11.0-rc.10 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 14 Jun 2023 i
  • Highest CVSS 7.1 i
  • With no published fix 1 i
  • Stars 821 i
  • OpenSSF scorecard 3/10 i
  • Licence Apache-2.0 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.Build.NuGetSdkResolver, 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
5.10.0-rc.7240 — H1 Apache-2.0 No Details →
5.11.0-rc.10 — H1 Apache-2.0 No Details →
5.9.0-rc.7122 — H1 Apache-2.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.Build.NuGetSdkResolver

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-29337: NuGet Client Remote Code Execution Vulnerability 7.1 high No fix published 14 Jun 2023

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.Build.NuGetSdkResolver

Is Microsoft.Build.NuGetSdkResolver safe to use?

Vulert records 1 vulnerabilities for Microsoft.Build.NuGetSdkResolver in NuGet: 0 critical, 1 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is Microsoft.Build.NuGetSdkResolver's Vulert package health score?

Vulert scores Microsoft.Build.NuGetSdkResolver 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of Microsoft.Build.NuGetSdkResolver affected?

Yes. 5.11.0-rc.10, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of Microsoft.Build.NuGetSdkResolver should I use?

5.11.0-rc.10 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.Build.NuGetSdkResolver have?

1 vulnerability is recorded for Microsoft.Build.NuGetSdkResolver in the NuGet ecosystem: 0 critical, 1 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.Build.NuGetSdkResolver vulnerabilities disclosed?

0 vulnerabilities were recorded for Microsoft.Build.NuGetSdkResolver in the last 12 months, and the oldest entry in this database dates to 14 Jun 2023. 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.Build.NuGetSdkResolver 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.Build.NuGetSdkResolver for upcoming vulnerabilities?

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