Is Microsoft.Build.Tasks.Core 16.11 vulnerable?

NuGet · 2 releases from 16.11.0 to 16.11.6 · latest Microsoft.Build.Tasks.Core is 18.12.2 · checked 18 Nov 2026

No known advisories in the last release

Microsoft.Build.Tasks.Core 16.11.6, the last 16.11 release, has no known advisories. 1 advisory affects earlier 16.11.x releases, so update to 16.11.6.

Update within 16.11:dotnet add package Microsoft.Build.Tasks.Core --version 16.11.6

Is your project on an affected Microsoft.Build.Tasks.Core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 16.11.x, affecting earlier releases

  • HighCVE-2025-26646GHSA-h4j7-5rxr-p4wc13 May 2025

    Microsoft.Build.Tasks.Core .NET Spoofing Vulnerability

    Affected
    >=15.8.166 <15.9.30 · >=16.0.461 <16.11.6 · >=17.0.0 <17.8.29 · >=17.9.5 <17.10.29 · >=17.11.4 <17.12.36 · >=17.12.6 <17.13.26 · >=17.13.9 <17.14.8
    Fixed in
    15.9.30, 16.11.6, 17.8.29, 17.10.29, 17.12.36, 17.13.26, 17.14.8

Every Microsoft.Build.Tasks.Core 16.11.x release

Affected: 16.11.0. 16.11.6 is not affected. Latest Microsoft.Build.Tasks.Core: 18.12.2.

VersionKnown advisories
Microsoft.Build.Tasks.Core 16.11.6None
Microsoft.Build.Tasks.Core 16.11.0CVE-2025-26646

Which of your client projects are still on Microsoft.Build.Tasks.Core 16.11?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.Build.Tasks.Core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other Microsoft.Build.Tasks.Core versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.