Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

CVE-2025-55247 — Microsoft.Build.Tasks.Core

HIGH

CVE-2025-55247 is a high-severity (CVSS 7.3) CWE-59 vulnerability in Microsoft.Build.Tasks.Core. A fix is available for Microsoft.Build.Tasks.Core — see the affected versions and patch details below.

Microsoft Security Advisory CVE-2025-55247 | .NET Denial of Service Vulnerability

Also known asBIT-dotnet-2025-55247BIT-dotnet-sdk-2025-55247GHSA-w3q9-fxm7-j8fq
Published
Oct 14, 2025
Updated
Apr 10, 2026
Affected
18 pkgs
Patched
18 / 18
Exploits
None indexed
Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-55247.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2025-55247 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

18 pkgs affected
.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.Tasks.Core.NETMicrosoft.Build.NETMicrosoft.Build+10 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft Security Advisory CVE-2025-55247 | .NET Denial of Service Vulnerability

<a name="executive-summary"></a>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

<a name="mitigation-factors"></a>Mitigation factors

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

<a name="affected-software"></a>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.

<a name="affected-packages"></a>Affected Packages

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

Package nameAffected versionPatched version
Microsoft.Build.Tasks.Core17.15.0-preview-25277-114 <br />>=17.14.0, <= 17.14.8 <br />>= 17.12.0, <= 17.12.36 <br/> >= 17.11.0, <= 17.11.31<br /> >= 17.10.0, <= 17.10.29 <br /> >= 17.8.0, <= 17.8.29 <br />18.0.0-preview-25476-107 <br />17.14.28 <br />17.12.50 <br/>17.11.48 <br />17.10.46 <br />17.8.43 <br />
Package nameAffected versionPatched version
Microsoft.Build17.15.0-preview-25277-114 <br />>=17.14.0, <= 17.14.8 <br />>= 17.12.0, <= 17.12.36 <br/> >= 17.11.0, <= 17.11.31<br /> >= 17.10.0, <= 17.10.29 <br /> >= 17.8.0, <= 17.8.29 <br />18.0.0-preview-25476-107 <br />17.14.28 <br />17.12.50 <br/>17.11.48 <br />17.10.46 <br />17.8.43 <br />
Package nameAffected versionPatched version
Microsoft.Build.Utilities.core17.15.0-preview-25277-114 <br />>=17.14.0, <= 17.14.8 <br />>= 17.12.0, <= 17.12.36 <br/> >= 17.11.0, <= 17.11.31<br /> >= 17.10.0, <= 17.10.29 <br /> >= 17.8.0, <= 17.8.29 <br />18.0.0-preview-25476-107 <br />17.14.28 <br />17.12.50 <br/>17.11.48 <br />17.10.46 <br />17.8.43 <br />

Advisory FAQ

<a name="how-affected"></a>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 or affected packages, you're exposed to the vulnerability.

<a name="how-fix"></a>How do I fix the issue?

  1. 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.
  2. 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.

Other Information

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 [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

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

Revisions

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

Affected Packages

18 total 18 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.15.0-preview-25277-114&&< 18.0.0-preview-25476-10718.0.0-preview-25476-107dotnet add package Microsoft.Build.Tasks.Core --version 18.0.0-preview-25476-107
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.14.0&&< 17.14.2817.14.28dotnet add package Microsoft.Build.Tasks.Core --version 17.14.28
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.12.0&&< 17.12.5017.12.50dotnet add package Microsoft.Build.Tasks.Core --version 17.12.50
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.11.0&&< 17.11.4817.11.48dotnet add package Microsoft.Build.Tasks.Core --version 17.11.48
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.10.0&&< 17.10.4617.10.46dotnet add package Microsoft.Build.Tasks.Core --version 17.10.46
.NETNuGetMicrosoft.Build.Tasks.Core≥ 17.8.0&&< 17.8.4317.8.43dotnet add package Microsoft.Build.Tasks.Core --version 17.8.43

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.Build.Tasks.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update Microsoft.Build.Tasks.Core to 18.0.0-preview-25476-107 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55247 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-55247 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-55247. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The Red Hat Product Security team has assessed this issue as Moderate. Predictable MSBuild temporary directory paths on Linux allow a local user to precreate or manipulate build temp directories, causing build failures (denial of service) on shared build hosts or CI runners using the affected .NET packages. ``` .NET…

ProductFixed inAdvisory
Red Hat Enterprise Linux 10dotnet8.0-0:8.0.121-1.el10_0RHSA-2025:18152
Red Hat Enterprise Linux 10dotnet9.0-0:9.0.111-1.el10_0RHSA-2025:18153
Red Hat Enterprise Linux 10dotnet10.0-0:10.0.100~rc.2.25502.107-0.12.el10_1RHBA-2025:20993
Red Hat Enterprise Linux 8dotnet8.0-0:8.0.121-1.el8_10RHSA-2025:18148
Red Hat Enterprise Linux 8dotnet9.0-0:9.0.111-1.el8_10RHSA-2025:18150
Red Hat Enterprise Linux 9dotnet10.0-0:10.0.100~rc.2.25502.107-0.10.el9_7RHBA-2025:20916
Red Hat Enterprise Linux 9dotnet8.0-0:8.0.121-1.el9_6RHSA-2025:18149
Red Hat Enterprise Linux 9dotnet9.0-0:9.0.111-1.el9_6RHSA-2025:18151

Frequently Asked Questions

# Microsoft Security Advisory CVE-2025-55247 | .NET Denial of Service Vulnerability ## <a name="executive-summary"></a>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 affe
O3 Security · Impact-Aware SCA

Is CVE-2025-55247 in your dependencies?

O3 Security finds CVE-2025-55247 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2025-55247: DoS (High 7.3) | O3 Security