Microsoft.NET.Build.Containers vulnerabilities

Tasks and targets to natively publish .NET applications as containers.

Registry
NuGet
Latest
10.0.303
License
MIT

2 known advisories

The latest version, 10.0.303, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package Microsoft.NET.Build.Containers --version 10.0.303

Is your project on an affected Microsoft.NET.Build.Containers?

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

Security advisories for Microsoft.NET.Build.Containers

  • HighCVE-2026-50526GHSA-55jh-fwmh-39m421 Jul 2026

    Microsoft Security Advisory CVE-2026-50526 – .NET Tampering Vulnerability

    Affected
    >=10.0.0 <10.0.10 · >=9.0.0 <9.0.18 · >=8.0.0 <8.0.29
    Fixed in
    8.0.29, 9.0.18, 10.0.10
  • HighCVE-2023-35390GHSA-p8rx-fwgq-rh2f9 Aug 2023

    .NET Remote Code Execution Vulnerability

    Affected
    <7.0.307
    Fixed in
    7.0.307

Is your Microsoft.NET.Build.Containers version vulnerable?

Which of your client projects still run an old Microsoft.NET.Build.Containers?

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.