Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

.NET, Visual Studio, and Build Tools for Visual Studio Spoofing Vulnerability

cve-program · CVE-2025-26646

Published

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

Read the publisher's advisory

euvd · EUVD-2025-14511

Published

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

Read the publisher's advisory

nvd · CVE-2025-26646

Published

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

Read the publisher's advisory

osv · GHSA-h4j7-5rxr-p4wc

Published

# Microsoft Security Advisory CVE-2025-26646: .NET Spoofing Vulnerability ## <a name="executive-summary"></a>Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 9.0.xxx and .NET 8.0.xxx SDK. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability. A vulnerability exists in .NET SDK or MSBuild applications where external control of file name or path allows an unauthorized attacked to perform spoofing over a network. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/356 ### <a name="mitigation-factors"></a>Mitigation factors Projects which do not utilize the [DownloadFile](https://learn.microsoft.com/visualstudio/msbuild/downloadfile-task) build task are not susceptible to this vulnerability. ## <a name="affected-software"></a>Affected software * Any installation of .NET 9.0.105 SDK, .NET 9.0.203 SDK or earlier. * Any installation of .NET 8.0.115 SDK, .NET 8.0.311 or .NET 8.0.312 SDK, .NET 8.0.408 or .NET 8.0.409 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 name | Affected version | Patched version ------------ | ---------------- | ------------------------- [Microsoft.Build.Tasks.Core](https://www.nuget.org/packages/Microsoft.Build.Tasks.Core) |>= 15.8.166, <=15.9.20<br />>=16.0.461, <= 16.11.0<br />>= 17.0.0, <= 17.8.3<br/>>= 17.9.5, <= 17.10.4<br />17.11.4<br />17.12.6 <br />17.13.9 | 15.9.30<br />16.11.6<br />17.8.29<br/>17.10.29<br />17.12.36<br />17.13.26 <br />17.14.8 ## 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](#affected-packages) or [affected packages](#affected-software), 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 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 ``` * If you're using .NET 9.0, you should download and install the appropriate SDK: `.NET 9.0.300` for Visual Studio 2022 v17.14, `.NET 9.0.204` for v17.13, or `.NET 9.0.106` for v17.12. Download from https://dotnet.microsoft.com/download/dotnet-core/9.0. * If you're using .NET 8.0, you should download and install the appropriate SDK: `.NET 8.0.410` for Visual Studio 2022 v17.11, `.NET 8.0.313` for v17.10, or `.NET 8.0.116` for v17.8. Download from https://dotnet.microsoft.com/download/dotnet-core/8.0. 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 or .NET 9.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/aspnetcore. 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.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2025-26646

No CISA KEV listing is included in this saved record. Exploitation may still have occurred.

FIRST EPSS: 1.29 % · percentile 70.67 % · scored 14 Nov 2026.

Saved 14 Nov 2026 16:37:01 UTC · View this risk record (JSON)

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

CVE-2025-26646 · 14 Nov 2026 16:37:01 UTC

CVE-2025-26646 · 13 Nov 2026 19:59:34 UTC

CVE-2025-26646 · 12 Nov 2026 18:18:51 UTC

CVE-2025-26646 · 10 Nov 2026 20:24:10 UTC

CVE-2025-26646 · 09 Nov 2026 21:04:24 UTC

CVE-2025-26646 · 08 Nov 2026 15:12:21 UTC

CVE-2025-26646 · 07 Nov 2026 16:07:52 UTC

CVE-2025-26646 · 06 Nov 2026 19:10:17 UTC

CVE-2025-26646 · 05 Nov 2026 22:49:22 UTC

CVE-2025-26646 · 05 Nov 2026 02:54:06 UTC

CVE-2025-26646 · 03 Nov 2026 16:59:18 UTC

CVE-2025-26646 · 02 Nov 2026 23:59:04 UTC

CVE-2025-26646 · 01 Nov 2026 23:58:58 UTC

CVE-2025-26646 · 01 Nov 2026 03:04:52 UTC

CVE-2025-26646 · 31 Oct 2026 01:52:30 UTC

CVE-2025-26646 · 29 Oct 2026 18:29:26 UTC

CVE-2025-26646 · 28 Oct 2026 19:55:37 UTC

CVE-2025-26646 · 27 Oct 2026 15:46:19 UTC

CVE-2025-26646 · 27 Oct 2026 00:23:05 UTC

CVE-2025-26646 · 25 Oct 2026 15:18:41 UTC

CVE-2025-26646 · 25 Oct 2026 02:24:38 UTC

CVE-2025-26646 · 23 Oct 2026 16:01:26 UTC

Advisory history

13 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

15 Nov 2026 03:39:23 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

13 Nov 2026 03:26:11 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

11 Nov 2026 02:46:41 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

9 Nov 2026 02:16:13 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

7 Nov 2026 01:31:21 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

5 Nov 2026 01:05:26 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

3 Nov 2026 00:03:54 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

31 Oct 2026 23:10:47 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

29 Oct 2026 22:53:57 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

27 Oct 2026 21:55:02 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

euvd · EUVD-2025-14511 · Published

25 Oct 2026 02:24:42 UTC

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

nvd · CVE-2025-26646 · Published

23 Oct 2026 15:48:27 UTC

.NET, Visual Studio, and Build Tools for Visual Studio Spoofing Vulnerability

cve-program · CVE-2025-26646 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 12:11 UTC · 256 of 275 readable · 252 fully read · documentation 469/469 current