nuget package report

Is Microsoft.Build.Utilities.Core safe?

1 known vulnerability, worst severity HIGH.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so nuget packages are not covered.


      cvss
      0.0
      high

      severity out of 10

      epss
      0.00%
      medium

      chance of exploitation in 30 days, 47th percentile of all CVEs

      xyz score
      0.0
      low

      CyberXYZ composite out of 10

      fig. 01 — GHSA-w3q9-fxm7-j8fq, the advisory selected below

      // 1 advisories

      GHSA-w3q9-fxm7-j8fq

      HIGHCVE-2025-55247
      // executive summary

      Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0.xxx, .NET 9.0.xxx and .NET 10.0.xxx. This advisory also provides guidance on what developers can do to update their environments to remove this vulnerability.

      A vulnerability exists in .NET where predictable paths for MSBuild's temporary directories on Linux let another user create the directories ahead of MSBuild, leading to DoS of builds. This only affects .NET on Linux operating systems.

      // announcement

      Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/370

      // mitigation factors

      Projects which do not utilize the DownloadFile build task are not susceptible to this vulnerability.

      // affected software
      • Any installation of .NET 10.0.100-rc.1.25451.107 SDK or earlier.
      • Any installation of .NET 9.0.110 SDK, .NET 9.0.305 SDK or earlier.
      • Any installation of .NET 8.0.120 SDK, .NET 8.0.317 SDK, .NET 8.0.414 SDK or earlier.
      // affected packages

      The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below

      Package name |Affected version | Patched version ------------ |---------------- | ------------------------- Microsoft.Build.Tasks.Core | 17.15.0-preview-25277-114 >=17.14.0, >= 17.12.0, >= 17.11.0, >= 17.10.0, >= 17.8.0, | 18.0.0-preview-25476-107 17.14.28 17.12.50 17.11.48 17.10.46 17.8.43

      Package name|Affected version | Patched version ------------ |---------------|---------------- Microsoft.Build | 17.15.0-preview-25277-114 >=17.14.0, >= 17.12.0, >= 17.11.0, >= 17.10.0, >= 17.8.0, | 18.0.0-preview-25476-107 17.14.28 17.12.50 17.11.48 17.10.46 17.8.43

      Package name |Affected version | Patched version ------------ |---------------|---------------- Microsoft.Build.Utilities.core| 17.15.0-preview-25277-114 >=17.14.0, >= 17.12.0, >= 17.11.0, >= 17.10.0, >= 17.8.0, | 18.0.0-preview-25476-107 17.14.28 17.12.50 17.11.48 17.10.46 17.8.43

      // how do i know if i am affected?

      If you have a .NET SDK with a version listed, or an affected package listed in [affected software](#affected-packages) or [affected packages](#affected-software), you're exposed to the vulnerability.

      // how do i fix the issue?
      • To fix the issue please install the latest version of .NET 10.0 SDK, .NET 9.0 SDK or .NET 8.0 SDK. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
      • If your application references the vulnerable package, update the package reference to the patched version.
      • You can list the versions you have installed by running the dotnet --info command. You will see output like the following;
      .NET SDK:
       Version:           9.0.100
       Commit:            59db016f11
       Workload version:  9.0.100-manifests.3068a692
       MSBuild version:   17.12.7+5b8665660
      
      Runtime Environment:
       OS Name:     Mac OS X
       OS Version:  15.2
       OS Platform: Darwin
       RID:         osx-arm64
       Base Path:   /usr/local/share/dotnet/sdk/9.0.100/
      
      .NET workloads installed:
      There are no installed workloads to display.
      Configured to use loose manifests when installing new manifests.
      
      Host:
        Version:      9.0.0
        Architecture: arm64
        Commit:       9d5a6a9aa4
      
      .NET SDKs installed:
        9.0.100 [/usr/local/share/dotnet/sdk]
      
      .NET runtimes installed:
        Microsoft.AspNetCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
        Microsoft.NETCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
      
      Other architectures found:
        x64   [/usr/local/share/dotnet]
          registered at [/etc/dotnet/install_location_x64]
      
      Environment variables:
        Not set
      
      global.json file:
        Not found
      
      Learn more:
        https://aka.ms/dotnet/info
      
      Download .NET:
        https://aka.ms/dotnet/download

      Once you have installed the updated SDK, restart your apps for the update to take effect.

      // reporting security issues

      If you have found a potential security issue in .NET 8.0, .NET 9.0 or .NET 10.0, please email details to secure@microsoft.com. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at .

      // support

      You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

      // disclaimer

      The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

      // external links

      [CVE-2025-55247]( https://www.cve.org/CVERecord?id=CVE-2025-55247)

      // revisions

      V1.0 (October 14, 2025): Advisory published.

      // cvss v3.1 vector

      CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

      Attack vector
      Local
      Attack complexity
      Low
      Privileges required
      Low
      User interaction
      Required
      Scope
      Unchanged
      Confidentiality
      High
      Integrity
      High
      Availability
      High

      Checked 2026-09-28 at 19:47 UTC. The most recent advisory here was published 2025-10-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.