Is Microsoft.Build 17.11 vulnerable?
NuGet · 3 releases from 17.11.4 to 17.11.48 · latest Microsoft.Build is 18.12.2 · checked 18 Nov 2026
No known advisories in the last release
Microsoft.Build 17.11.48, the last 17.11 release, has no known advisories. 1 advisory affects earlier 17.11.x releases, so update to 17.11.48.
dotnet add package Microsoft.Build --version 17.11.48Is 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
Fixed within 17.11.x, affecting earlier releases
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
Every Microsoft.Build 17.11.x release
Affected: 17.11.4 to 17.11.31. 17.11.48 is not affected. Latest Microsoft.Build: 18.12.2.
| Version | Known advisories |
|---|---|
| Microsoft.Build 17.11.48 | None |
| Microsoft.Build 17.11.31 | CVE-2025-55247 |
| Microsoft.Build 17.11.4 | CVE-2025-55247 |
Which of your client projects are still on Microsoft.Build 17.11?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.Build version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.Build 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.