What is GHSA-G4VJ-CJJJ-V7HG?

GHSA-G4VJ-CJJJ-V7HG is a low-severity security vulnerability in NuGet.Packaging (nuget), affecting versions >= 4.9.0, <= 4.9.6. It is fixed in 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1.

Which packages are affected by GHSA-G4VJ-CJJJ-V7HG?

NuGet.Packaging (nuget) versions >= 4.9.0, = 4.9.0, = 4.9.0, <= 4.9.6.

Is there a fix for GHSA-G4VJ-CJJJ-V7HG?

Yes. GHSA-G4VJ-CJJJ-V7HG is fixed in 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1. Upgrade to this version or later.

Is GHSA-G4VJ-CJJJ-V7HG exploitable, and should I be worried?

Whether GHSA-G4VJ-CJJJ-V7HG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-G4VJ-CJJJ-V7HG is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-G4VJ-CJJJ-V7HG in NuGet.Packaging

Q: Which packages are affected by GHSA-G4VJ-CJJJ-V7HG?

NuGet.Packaging (nuget) versions >= 4.9.0, = 4.9.0, = 4.9.0, <= 4.9.6.

Q: Is there a fix for GHSA-G4VJ-CJJJ-V7HG?

Yes. GHSA-G4VJ-CJJJ-V7HG is fixed in 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1. Upgrade to this version or later.

Q: Is GHSA-G4VJ-CJJJ-V7HG exploitable, and should I be worried?

Whether GHSA-G4VJ-CJJJ-V7HG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-G4VJ-CJJJ-V7HG is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-G4VJ-CJJJ-V7HG?

Upgrade: NuGet.Packaging to 4.9.7 or later, NuGet.Packaging to 5.11.7 or later, NuGet.Packaging to 6.8.2 or later, NuGet.Packaging to 6.11.2 or later, NuGet.Packaging to 6.12.5 or later, NuGet.Packaging to 6.14.3 or later, NuGet.Packaging to 7.0.3 or later, NuGet.Packaging to 7.3.1 or later, NuGet.Protocol to 4.9.7 or later, NuGet.Protocol to 5.11.7 or later, NuGet.Protocol to 6.8.2 or later, NuGet.Protocol to 6.11.2 or later, NuGet.Protocol to 6.12.5 or later, NuGet.Protocol to 6.14.3 or later, NuGet.Protocol to 7.0.3 or later, NuGet.Protocol to 7.3.1 or later, NuGet.CommandLine to 4.9.7 or later, NuGet.CommandLine to 5.11.7 or later, NuGet.CommandLine to 6.8.2 or later, NuGet.CommandLine to 6.11.2 or later, NuGet.CommandLine to 6.12.5 or later, NuGet.CommandLine to 6.14.3 or later, NuGet.CommandLine to 7.0.3 or later, NuGet.CommandLine to 7.3.1 or later.

Summary

Defense in Depth update for NuGet Client

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

Impact

This update adds validation of the package ID and version during package download, in addition to the existing package signature validation.

Affected versions

NuGet.Packaging (>= 4.9.0, <= 4.9.6) NuGet.Packaging (>= 5.11.0, <= 5.11.6) NuGet.Packaging (>= 6.8.0, <= 6.8.1) NuGet.Packaging (>= 6.11.0, <= 6.11.1) NuGet.Packaging (>= 6.12.0, <= 6.12.4) NuGet.Packaging (>= 6.14.0, <= 6.14.2) NuGet.Packaging (>= 7.0.0, <= 7.0.2) NuGet.Packaging (= 7.3.0) NuGet.Protocol (>= 4.9.0, <= 4.9.6) NuGet.Protocol (>= 5.11.0, <= 5.11.6) NuGet.Protocol (>= 6.8.0, <= 6.8.1) NuGet.Protocol (>= 6.11.0, <= 6.11.1) NuGet.Protocol (>= 6.12.0, <= 6.12.4) NuGet.Protocol (>= 6.14.0, <= 6.14.2) NuGet.Protocol (>= 7.0.0, <= 7.0.2) NuGet.Protocol (= 7.3.0) NuGet.CommandLine (>= 4.9.0, <= 4.9.6) NuGet.CommandLine (>= 5.11.0, <= 5.11.6) NuGet.CommandLine (>= 6.8.0, <= 6.8.1) NuGet.CommandLine (>= 6.11.0, <= 6.11.1) NuGet.CommandLine (>= 6.12.0, <= 6.12.4) NuGet.CommandLine (>= 6.14.0, <= 6.14.2) NuGet.CommandLine (>= 7.0.0, <= 7.0.2) NuGet.CommandLine (= 7.3.0)

Security releases

NuGet.Packaging → 4.9.7 (nuget) NuGet.Packaging → 5.11.7 (nuget) NuGet.Packaging → 6.8.2 (nuget) NuGet.Packaging → 6.11.2 (nuget) NuGet.Packaging → 6.12.5 (nuget) NuGet.Packaging → 6.14.3 (nuget) NuGet.Packaging → 7.0.3 (nuget) NuGet.Packaging → 7.3.1 (nuget) NuGet.Protocol → 4.9.7 (nuget) NuGet.Protocol → 5.11.7 (nuget) NuGet.Protocol → 6.8.2 (nuget) NuGet.Protocol → 6.11.2 (nuget) NuGet.Protocol → 6.12.5 (nuget) NuGet.Protocol → 6.14.3 (nuget) NuGet.Protocol → 7.0.3 (nuget) NuGet.Protocol → 7.3.1 (nuget) NuGet.CommandLine → 4.9.7 (nuget) NuGet.CommandLine → 5.11.7 (nuget) NuGet.CommandLine → 6.8.2 (nuget) NuGet.CommandLine → 6.11.2 (nuget) NuGet.CommandLine → 6.12.5 (nuget) NuGet.CommandLine → 6.14.3 (nuget) NuGet.CommandLine → 7.0.3 (nuget) NuGet.CommandLine → 7.3.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

NuGet.Packaging to 4.9.7 or later; NuGet.Packaging to 5.11.7 or later; NuGet.Packaging to 6.8.2 or later; NuGet.Packaging to 6.11.2 or later; NuGet.Packaging to 6.12.5 or later; NuGet.Packaging to 6.14.3 or later; NuGet.Packaging to 7.0.3 or later; NuGet.Packaging to 7.3.1 or later; NuGet.Protocol to 4.9.7 or later; NuGet.Protocol to 5.11.7 or later; NuGet.Protocol to 6.8.2 or later; NuGet.Protocol to 6.11.2 or later; NuGet.Protocol to 6.12.5 or later; NuGet.Protocol to 6.14.3 or later; NuGet.Protocol to 7.0.3 or later; NuGet.Protocol to 7.3.1 or later; NuGet.CommandLine to 4.9.7 or later; NuGet.CommandLine to 5.11.7 or later; NuGet.CommandLine to 6.8.2 or later; NuGet.CommandLine to 6.11.2 or later; NuGet.CommandLine to 6.12.5 or later; NuGet.CommandLine to 6.14.3 or later; NuGet.CommandLine to 7.0.3 or later; NuGet.CommandLine to 7.3.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-G4VJ-CJJJ-V7HG? GHSA-G4VJ-CJJJ-V7HG is a low-severity security vulnerability in NuGet.Packaging (nuget), affecting versions >= 4.9.0, <= 4.9.6. It is fixed in 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1.
Which packages are affected by GHSA-G4VJ-CJJJ-V7HG?
- NuGet.Packaging (nuget) (versions >= 4.9.0, <= 4.9.6)
- NuGet.Protocol (nuget) (versions >= 4.9.0, <= 4.9.6)
- NuGet.CommandLine (nuget) (versions >= 4.9.0, <= 4.9.6)
Is there a fix for GHSA-G4VJ-CJJJ-V7HG? Yes. GHSA-G4VJ-CJJJ-V7HG is fixed in 4.9.7, 5.11.7, 6.8.2, 6.11.2, 6.12.5, 6.14.3, 7.0.3, 7.3.1. Upgrade to this version or later.
Is GHSA-G4VJ-CJJJ-V7HG exploitable, and should I be worried? Whether GHSA-G4VJ-CJJJ-V7HG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-G4VJ-CJJJ-V7HG is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-G4VJ-CJJJ-V7HG?
- Upgrade NuGet.Packaging to 4.9.7 or later
- Upgrade NuGet.Packaging to 5.11.7 or later
- Upgrade NuGet.Packaging to 6.8.2 or later
- Upgrade NuGet.Packaging to 6.11.2 or later
- Upgrade NuGet.Packaging to 6.12.5 or later
- Upgrade NuGet.Packaging to 6.14.3 or later
- Upgrade NuGet.Packaging to 7.0.3 or later
- Upgrade NuGet.Packaging to 7.3.1 or later
- Upgrade NuGet.Protocol to 4.9.7 or later
- Upgrade NuGet.Protocol to 5.11.7 or later
- Upgrade NuGet.Protocol to 6.8.2 or later
- Upgrade NuGet.Protocol to 6.11.2 or later
- Upgrade NuGet.Protocol to 6.12.5 or later
- Upgrade NuGet.Protocol to 6.14.3 or later
- Upgrade NuGet.Protocol to 7.0.3 or later
- Upgrade NuGet.Protocol to 7.3.1 or later
- Upgrade NuGet.CommandLine to 4.9.7 or later
- Upgrade NuGet.CommandLine to 5.11.7 or later
- Upgrade NuGet.CommandLine to 6.8.2 or later
- Upgrade NuGet.CommandLine to 6.11.2 or later
- Upgrade NuGet.CommandLine to 6.12.5 or later
- Upgrade NuGet.CommandLine to 6.14.3 or later
- Upgrade NuGet.CommandLine to 7.0.3 or later
- Upgrade NuGet.CommandLine to 7.3.1 or later

Other vulnerabilities in NuGet.Packaging

CVE-IDSeverityPackage summary

CVE-2024-0057CriticalNuGet.CommandLine: NuGet Client Security Feature Bypass Vulnerability