Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
5.11.76.14.36.11.26.12.57.3.16.8.24.9.77.0.3· Vendor fix available
Issue
Impact This update adds validation of the package ID and version during package download, in addition to the existing package signature validation. Patches NuGet The following NuGet.exe, NuGet.CommandLine, NuGet.Packaging, and NuGet.Protocol versions have been patched: |Affected versions|Patched version| |--|--| |= 4.9.0, <= 4.9.6|4.9.7| |= 5.11.0, <= 5.11.6|5.11.7| |= 6.8.0, <= 6.8.1|6.8.2| |= 6.11.0, <= 6.11.1|6.11.2| |= 6.12.0, <= 6.12.4|6.12.5| |= 6.14.0, <= 6.14.2|6.14.3| |= 7.0.0, <= 7.0.2|7.0.3| |7.3.0|7.3.1| .NET SDK .NET 8.0.126 SDK .NET 8.0.420 SDK .NET 9.0.116 SDK .NET 9.0.313 SDK .NET 10.0.106 SDK .NET 10.0.202 SDK Workarounds N/A References https://github.com/NuGet/NuGetGallery/security/advisories/GHSA-9r3h-v4hx-rhfr Credit splitline with DEVCORE
Recommended action: Upgrade to 7.3.1, 7.0.3, 6.14.3 or 5 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
5.11.66.6.26.8.16.3.46.7.16.4.36.0.6· Vendor fix available
Issue
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…
Recommended action: Upgrade to 6.8.1, 6.7.1, 6.6.2 or 4 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.