Which versions of moq are affected by GHSA-6R78-M64M-QWCF?

moq (nuget) versions >= 4.20.0-rc, < 4.20.2 is affected.

Is there a fix for GHSA-6R78-M64M-QWCF?

Yes. GHSA-6R78-M64M-QWCF is fixed in 4.20.2. Upgrade to this version or later.

Is GHSA-6R78-M64M-QWCF exploitable, and should I be worried?

Whether GHSA-6R78-M64M-QWCF 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-6R78-M64M-QWCF 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-6R78-M64M-QWCF in moq

Q: What is GHSA-6R78-M64M-QWCF?

GHSA-6R78-M64M-QWCF is a low-severity security vulnerability in moq (nuget), affecting versions >= 4.20.0-rc, < 4.20.2. It is fixed in 4.20.2.

Q: Is there a fix for GHSA-6R78-M64M-QWCF?

Yes. GHSA-6R78-M64M-QWCF is fixed in 4.20.2. Upgrade to this version or later.

Q: Is GHSA-6R78-M64M-QWCF exploitable, and should I be worried?

Whether GHSA-6R78-M64M-QWCF 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-6R78-M64M-QWCF 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-6R78-M64M-QWCF?

Upgrade moq to 4.20.2 or later.

GHSA-6R78-M64M-QWCF

GHSA-6R78-M64M-QWCF is a low-severity security vulnerability in moq (nuget), affecting versions >= 4.20.0-rc, < 4.20.2. It is fixed in 4.20.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Moq v4.20.0-rc to 4.20.1 share hashed user data

Moq v4.20.0-rc to 4.20.1 include support for SponsorLink, which runs an obfuscated DLL at build time that scans local git config data and shares the user's hashed email address with SponsorLink's remote servers. There is no option to disable this.

Moq v4.20.2 has removed this functionality.

Impact

Affected versions

moq (>= 4.20.0-rc, < 4.20.2)

Security releases

moq → 4.20.2 (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 moq to 4.20.2 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is GHSA-6R78-M64M-QWCF? GHSA-6R78-M64M-QWCF is a low-severity security vulnerability in moq (nuget), affecting versions >= 4.20.0-rc, < 4.20.2. It is fixed in 4.20.2.
Which versions of moq are affected by GHSA-6R78-M64M-QWCF? moq (nuget) versions >= 4.20.0-rc, < 4.20.2 is affected.
Is there a fix for GHSA-6R78-M64M-QWCF? Yes. GHSA-6R78-M64M-QWCF is fixed in 4.20.2. Upgrade to this version or later.
Is GHSA-6R78-M64M-QWCF exploitable, and should I be worried? Whether GHSA-6R78-M64M-QWCF 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-6R78-M64M-QWCF 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-6R78-M64M-QWCF? Upgrade moq to 4.20.2 or later.