Is Microsoft.Build.Tasks.Core 16.6 vulnerable?

NuGet · 1 release from 16.6.0 to 16.6.0 · latest Microsoft.Build.Tasks.Core is 18.12.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. Microsoft.Build.Tasks.Core 16.6.0, the last 16.6 release, is affected by 1 known security advisory (1 high), including CVE-2025-26646. Upgrade to 16.11.6 or later to fix all of them.

Upgrade with: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

Advisories affecting Microsoft.Build.Tasks.Core 16.6.0

  • 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

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

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.