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

NuGet Client Remote Code Execution Vulnerability

CVSS 3.1 7.1 HIGHEUVD CVSS 3.1 7.1 CVSS 3.1 · [email protected] · Secondary 7.1 HIGHCVSS_V3 Publisher rating HIGHFixed by NuGet.PackageManagement 6.0.5Fixed by NuGet.PackageManagement 6.2.4Fixed by NuGet.PackageManagement 6.3.3Fixed by NuGet.PackageManagement 6.4.2KEV status unknown

cve-program · CVE-2023-29337

Published

NuGet Client Remote Code Execution Vulnerability

Read the publisher's advisory

euvd · EUVD-2023-1715

Published

NuGet Client Remote Code Execution Vulnerability

Read the publisher's advisory

nvd · CVE-2023-29337

Published

NuGet Client Remote Code Execution Vulnerability

Read the publisher's advisory

osv · GHSA-6qmf-mmc7-6c2p

Published

### Description Microsoft is releasing this security advisory to provide information about a vulnerability in .NET and NuGet on Linux. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in .NET 6.0, .NET 7.0 and NuGet(nuget.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement) where a potential race condition that can lead to a symlink attack on Linux. Non-Linux platforms are not affected. ### Affected software This issue only affects Linux systems. #### NuGet & NuGet Packages - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.6.0 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.5.0 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.4.1 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.3.2 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.2.3 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 6.0.4 version or earlier. - Any NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, Microsoft.Build.NuGetSdkResolver, NuGet.PackageManagement 5.11.4 #### .NET SDK(s) - Any .NET SDK 7.0.106 or earlier, or 7.0.303 or earlier - Any .NET SDK 6.0.117 or earlier, or 6.0.312 or earlier, or 6.0.409 or earlier. ### Patches To fix the issue, please install the latest version of .NET 6.0 or .NET 7.0 and NuGet (NuGet.exe, NuGet.Protocol, NuGet.Common, NuGet.CommandLine, NuGet.Commands, NuGet.PackageManagement versions). 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 you're using NuGet.exe 6.6.0 or lower, you should download and install 6.6.1 from https://dist.nuget.org/win-x86-commandline/v6.6.1/nuget.exe. - If you're using NuGet.exe 6.5.0 or lower, you should download and install 6.5.1 from https://dist.nuget.org/win-x86-commandline/v6.5.1/nuget.exe. - If you're using NuGet.exe 6.4.1 or lower, you should download and install 6.4.2 from https://dist.nuget.org/win-x86-commandline/v6.4.2/nuget.exe. - If you're using NuGet.exe 6.3.2 or lower, you should download and install 6.3.3 from https://dist.nuget.org/win-x86-commandline/v6.3.3/nuget.exe. - If you're using NuGet.exe 6.2.3 or lower, you should download and install 6.2.4 from https://dist.nuget.org/win-x86-commandline/v6.2.4/nuget.exe. - If you're using NuGet.exe 6.0.4 or lower, you should download and install 6.0.5 from https://dist.nuget.org/win-x86-commandline/v6.0.5/nuget.exe. - If you're using NuGet.exe 5.11.4 or lower, you should download and install 5.11.5 from https://dist.nuget.org/win-x86-commandline/v5.11.5/nuget.exe. - If you're using .NET 7.0, you should download and install Runtime 7.0.7 or SDK 7.0.107 or SDK 7.0.304 from https://dotnet.microsoft.com/download/dotnet-core/7.0. - If you're using .NET 7.0, you should download and install Runtime 7.0.7 or SDK 7.0.107 or SDK 7.0.304 from https://dotnet.microsoft.com/download/dotnet-core/7.0. - If you're using .NET 6.0, you should download and install Runtime 6.0.18 or SDK 6.0.118 or SDK 6.0.312 from https://dotnet.microsoft.com/download/dotnet-core/6.0. ### Other details Announcement for this issue can be found at https://github.com/NuGet/Announcements/issues/69 MSRC details for this can be found at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-29337

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-2023-29337

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

FIRST EPSS: 1.15 % · percentile 67.33 % · scored 15 Nov 2026.

Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)

Risk history

Compare earlier KEV listings and 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. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

CVE-2023-29337 · 15 Nov 2026 14:45:34 UTC

CVE-2023-29337 · 14 Nov 2026 16:37:01 UTC

CVE-2023-29337 · 13 Nov 2026 19:59:34 UTC

CVE-2023-29337 · 12 Nov 2026 18:18:51 UTC

CVE-2023-29337 · 10 Nov 2026 20:24:10 UTC

CVE-2023-29337 · 09 Nov 2026 21:04:24 UTC

CVE-2023-29337 · 08 Nov 2026 15:12:21 UTC

CVE-2023-29337 · 07 Nov 2026 16:07:52 UTC

CVE-2023-29337 · 06 Nov 2026 19:10:17 UTC

CVE-2023-29337 · 05 Nov 2026 22:49:22 UTC

CVE-2023-29337 · 05 Nov 2026 02:54:06 UTC

CVE-2023-29337 · 03 Nov 2026 16:59:18 UTC

CVE-2023-29337 · 02 Nov 2026 23:59:04 UTC

CVE-2023-29337 · 01 Nov 2026 23:58:58 UTC

CVE-2023-29337 · 01 Nov 2026 03:04:52 UTC

CVE-2023-29337 · 31 Oct 2026 01:52:30 UTC

CVE-2023-29337 · 29 Oct 2026 18:29:26 UTC

CVE-2023-29337 · 28 Oct 2026 19:55:37 UTC

CVE-2023-29337 · 27 Oct 2026 15:46:19 UTC

CVE-2023-29337 · 27 Oct 2026 00:23:05 UTC

CVE-2023-29337 · 25 Oct 2026 15:18:41 UTC

CVE-2023-29337 · 25 Oct 2026 02:24:38 UTC

CVE-2023-29337 · 23 Oct 2026 16:01:26 UTC

Advisory history

14 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.

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 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current