How severe is GHSA-68w7-72jg-6qpp?

GHSA-68w7-72jg-6qpp has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-68w7-72jg-6qpp?

GHSA-68w7-72jg-6qpp affects the following packages: NuGet.CommandLine (NuGet), NuGet.Packaging (NuGet), NuGet.CommandLine (NuGet), NuGet.Packaging (NuGet), NuGet.CommandLine (NuGet), NuGet.Packaging (NuGet), NuGet.CommandLine (NuGet), NuGet.Packaging (NuGet), and 6 more. Ecosystems affected: NuGet.

How do I fix GHSA-68w7-72jg-6qpp?

Update NuGet.CommandLine to 5.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68w7-72jg-6qpp is resolved across your whole dependency graph.

How do I detect GHSA-68w7-72jg-6qpp in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for NuGet.CommandLine. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-68w7-72jg-6qpp if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-68w7-72jg-6qpp?

O3 pinpoints whether GHSA-68w7-72jg-6qpp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-68w7-72jg-6qpp actively exploited in the wild?

No public exploit code has been indexed for GHSA-68w7-72jg-6qpp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-68w7-72jg-6qpp?

GHSA-68w7-72jg-6qpp has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-68w7-72jg-6qpp?

GHSA-68w7-72jg-6qpp is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-68w7-72jg-6qpp published, and has it been updated?

GHSA-68w7-72jg-6qpp was published on February 13, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-68w7-72jg-6qpp

CRITICAL

NuGet Client Security Feature Bypass Vulnerability

Also known asBIT-dotnet-2024-0057BIT-dotnet-sdk-2024-0057BIT-powershell-2024-0057CVE-2024-0057

Published

Feb 13, 2024

Updated

Feb 4, 2026

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk84th percentile-0.86%

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.

Blast Radius

14 pkgs affected

.NETNuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging+6 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 is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 7.0 and .NET 8.0. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability.

A security feature bypass vulnerability exists when Microsoft .NET Framework-based applications use X.509 chain building APIs but do not completely validate the X.509 certificate due to a logic flaw. An attacker could present an arbitrary untrusted certificate with malformed signatures, triggering a bug in the framework. The framework will correctly report that X.509 chain building failed, but it will return an incorrect reason code for the failure. Applications which utilize this reason code to make their own chain building trust decisions may inadvertently treat this scenario as a successful chain build. This could allow an adversary to subvert the app's typical authentication logic.

Affected software

NuGet & NuGet Packages

Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.8.0 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.7.0 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.6.1 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.4.2 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.3.3 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.0.5 version or earlier.
Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 5.11.5 version or earlier.

.NET SDK(s)

Any .NET SDK 6.0.126 or earlier, or 6.0.418 or earlier.
Any .NET SDK 7.0.115 or earlier, or 7.0.312 or earlier, or 7.0.405 or earlier.
Any .NET SDK 8.0.101 or earlier.

Patches

To fix the issue, please install the latest version of .NET 6.0, .NET 7.0 or .NET 8.0 and NuGet (NuGet.exe, NuGet.CommandLine, NuGet. Packaging 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.8.0 or lower, you should download and install 6.8.1 from https://dist.nuget.org/win-x86-commandline/v6.8.1/nuget.exe.
If you're using NuGet.exe 6.7.0 or lower, you should download and install 6.7.1 from https://dist.nuget.org/win-x86-commandline/v6.7.1/nuget.exe.
If you're using NuGet.exe 6.6.1 or lower, you should download and install 6.6.2 from https://dist.nuget.org/win-x86-commandline/v6.6.2/nuget.exe.
If you're using NuGet.exe 6.4.2 or lower, you should download and install 6.4.3 from https://dist.nuget.org/win-x86-commandline/v6.4.3/nuget.exe.
If you're using NuGet.exe 6.3.3 or lower, you should download and install 6.3.4 from https://dist.nuget.org/win-x86-commandline/v6.3.4/nuget.exe.
If you're using NuGet.exe 6.0.5 or lower, you should download and install 6.0.6 from https://dist.nuget.org/win-x86-commandline/v6.0.6/nuget.exe.
If you're using NuGet.exe 5.11.5 or lower, you should download and install 5.11.6 from https://dist.nuget.org/win-x86-commandline/v5.11.6/nuget.exe.
If you're using .NET 8.0, you should download and install .NET 8.0.102 SDK (for Visual Studio 2022 v17.8) from https://dotnet.microsoft.com/download/dotnet-core/8.0 .
If you're using .NET 7.0, you should download and install SDK 7.0.116 (for Visual Studio 2022 v17.4), or SDK 7.0.313 (for Visual Studio 2022 v17.6), or 7.0.406 (for Visual Studio 2022 v17.7) from https://dotnet.microsoft.com/download/dotnet-core/7.0 .
If you're using .NET 6.0, you should download and install SDK 6.0.127 or SDK 6.0.419 (for Visual Studio 2022 v17.3) 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/71

MSRC details for this can be found at CVE-2024-0057 - Security Update Guide - Microsoft - NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability

Affected Packages

14 total 14 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`NuGet.CommandLine`	≥ 4.6.0&&< 5.11.6	5.11.6
.NETNuGet	`NuGet.Packaging`	≥ 4.6.0&&< 5.11.6	5.11.6
.NETNuGet	`NuGet.CommandLine`	≥ 6.0.0&&< 6.0.6	6.0.6
.NETNuGet	`NuGet.Packaging`	≥ 6.0.0&&< 6.0.6	6.0.6
.NETNuGet	`NuGet.CommandLine`	≥ 6.3.0&&< 6.3.4	6.3.4
.NETNuGet	`NuGet.Packaging`	≥ 6.3.0&&< 6.3.4	6.3.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for NuGet.CommandLine. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update NuGet.CommandLine to 5.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68w7-72jg-6qpp is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-68w7-72jg-6qpp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-68w7-72jg-6qpp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Description Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 7.0 and .NET 8.0. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability. A security feature bypass vulnerability exists when Microsoft .NET Framework-based applications use X.509 chain building APIs but do not completely validate the X.509 certificate due to a logic flaw. An attacker could present an arbitrary untrusted certificate with malformed signatures, triggering a bug in the framework. The frame

O3 Security · Impact-Aware SCA

Is GHSA-68w7-72jg-6qpp in your dependencies?

O3 detects GHSA-68w7-72jg-6qpp across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-68w7-72jg-6qpp

EPSS Exploitation Probability

Blast Radius

Description

Description

Affected software

NuGet & NuGet Packages

.NET SDK(s)

Patches

Other details

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-68w7-72jg-6qpp in your dependencies?