Is Microsoft.Build.Tasks.Core 16.10 vulnerable?
NuGet · 1 release from 16.10.0 to 16.10.0 · latest Microsoft.Build.Tasks.Core is 18.12.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. Microsoft.Build.Tasks.Core 16.10.0, the last 16.10 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.
dotnet add package Microsoft.Build.Tasks.Core --version 16.11.6Is your project on an affected Microsoft.Build.Tasks.Core?
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.10.0
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.10?
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
- Microsoft.Build.Tasks.Core 17.1
- Microsoft.Build.Tasks.Core 17.0
- Microsoft.Build.Tasks.Core 16.11
- Microsoft.Build.Tasks.Core 16.9
- Microsoft.Build.Tasks.Core 16.8
- Microsoft.Build.Tasks.Core 16.7
- Microsoft.Build.Tasks.Core 18.12
- Microsoft.Build.Tasks.Core 18.11
- Microsoft.Build.Tasks.Core 18.10
- Microsoft.Build.Tasks.Core 18.9
- Microsoft.Build.Tasks.Core 18.8
- Microsoft.Build.Tasks.Core 18.7
- All Microsoft.Build.Tasks.Core advisories
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.