Microsoft.Build vulnerabilities
This package contains the Microsoft.Build assembly which is used to create, edit, and evaluate MSBuild projects.
- Registry
- NuGet
- Latest
- 18.12.2
- License
- MIT
1 known advisory
The latest version, 18.12.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
dotnet add package Microsoft.Build --version 18.12.2Is your project on an affected Microsoft.Build?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for Microsoft.Build
Microsoft Security Advisory CVE-2025-55247 | .NET Denial of Service Vulnerability
- Affected
- >=17.15.0-preview-25277-114 <18.0.0-preview-25476-107 · >=17.14.0 <17.14.28 · >=17.12.0 <17.12.50 · >=17.11.0 <17.11.48 · >=17.10.0 <17.10.46 · >=17.8.0 <17.8.43
- Fixed in
- 17.8.43, 17.10.46, 17.11.48, 17.12.50, 17.14.28, 18.0.0-preview-25476-107
Is your Microsoft.Build version vulnerable?
- Microsoft.Build 18.12No known advisories in 18.12.2
- Microsoft.Build 18.11No known advisories in 18.11.0
- Microsoft.Build 18.10No known advisories in 18.10.1
- Microsoft.Build 18.9No known advisories in 18.9.6
- Microsoft.Build 18.8No known advisories in 18.8.2
- Microsoft.Build 18.7No known advisories in 18.7.1
- Microsoft.Build 17.14No known advisories in 17.14.28
- Microsoft.Build 17.13No known advisories in 17.13.26
- Microsoft.Build 17.12No known advisories in 17.12.50
- Microsoft.Build 17.11No known advisories in 17.11.48
- Microsoft.Build 17.10No known advisories in 17.10.46
- Microsoft.Build 17.9No known advisories in 17.9.5
- Microsoft.Build 16.11No known advisories in 16.11.6
- Microsoft.Build 16.10No known advisories in 16.10.0
- Microsoft.Build 16.9No known advisories in 16.9.0
- Microsoft.Build 16.8No known advisories in 16.8.0
- Microsoft.Build 16.7No known advisories in 16.7.0
- Microsoft.Build 16.6No known advisories in 16.6.0
Which of your client projects still run an old Microsoft.Build?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.