VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

moq: vulnerability history, versions and safety

moq is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Aug 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all moq vulnerabilities

Vulert verdict on moq 4.21.0 i

Updated on 23 Oct 2026

Good news: 4.21.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 4.21.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.21.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.21.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Aug 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 6,411 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for moq, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.21.0 24 Sep 2026 none BSD-3-Clause — Details →
4.20.72 07 Sep 2024 none BSD-3-Clause — Details →
4.20.70 28 Nov 2023 none BSD-3-Clause — Details →
4.20.69 11 Aug 2023 none BSD-3-Clause — Details →
4.18.4 30 Dec 2022 none non-standard — Details →
4.18.3 05 Dec 2022 none non-standard — Details →
4.18.2 02 Aug 2022 none non-standard — Details →
4.18.1 16 May 2022 none non-standard — Details →
4.18.0 11 May 2022 none non-standard — Details →
4.17.2 06 Mar 2022 none non-standard — Details →
4.17.1 26 Feb 2022 none non-standard — Details →
4.16.1 23 Feb 2021 none non-standard — Details →
4.16.0 16 Jan 2021 none non-standard — Details →
4.15.2 26 Nov 2020 none non-standard — Details →
4.15.1 10 Nov 2020 none non-standard — Details →
4.14.7 14 Oct 2020 none non-standard — Details →
4.14.6 30 Sep 2020 none non-standard — Details →
4.14.5 01 Jul 2020 none non-standard — Details →
4.14.4 24 Jun 2020 none non-standard — Details →
4.14.3 18 Jun 2020 none non-standard — Details →
4.14.2 16 Jun 2020 none non-standard — Details →
4.14.1 28 Apr 2020 none non-standard — Details →
4.14.0 24 Apr 2020 none non-standard — Details →
4.13.1 19 Oct 2019 none non-standard — Details →
4.13.0 31 Aug 2019 none non-standard — Details →
4.12.0 20 Jun 2019 none non-standard — Details →
4.11.0 27 May 2019 none non-standard — Details →
4.11.0-rc2 27 May 2019 none non-standard — Details →
4.11.0-rc1 19 Apr 2019 none non-standard — Details →
4.10.1 03 Dec 2018 none non-standard — Details →
4.10.0 08 Sep 2018 none non-standard — Details →
4.9.0 13 Jul 2018 none non-standard — Details →
4.8.3 09 Jun 2018 none non-standard — Details →
4.8.2 23 Feb 2018 none non-standard — Details →
4.8.1 08 Jan 2018 none non-standard — Details →
4.8.0 24 Dec 2017 none non-standard — Details →
4.8.0-rc1 08 Dec 2017 none non-standard — Details →
4.7.145 06 Nov 2017 none non-standard — Details →
4.7.142 10 Oct 2017 none non-standard — Details →
4.7.137 03 Oct 2017 none non-standard — Details →
4.7.127 25 Sep 2017 none non-standard — Details →
4.7.99 17 Jul 2017 none non-standard — Details →
4.7.63 21 Jun 2017 none non-standard — Details →
4.7.58 20 Jun 2017 none non-standard — Details →
4.7.49 18 Jun 2017 none non-standard — Details →
4.7.46 18 Jun 2017 none non-standard — Details →
4.7.25 02 Jun 2017 none non-standard — Details →
4.7.12 30 May 2017 none non-standard — Details →
4.7.11 30 May 2017 none non-standard — Details →
4.7.10 06 May 2017 none non-standard — Details →
4.7.9 29 Apr 2017 none non-standard — Details →
4.7.8 26 Mar 2017 none non-standard — Details →
4.7.7 25 Mar 2017 none non-standard — Details →
4.7.1 28 Feb 2017 none non-standard — Details →
4.7.0 22 Feb 2017 none non-standard — Details →
4.6.62-alpha 21 Feb 2017 none non-standard — Details →
4.6.39-alpha 18 Feb 2017 none non-standard — Details →
4.5.30 09 Jan 2017 none non-standard — Details →
4.5.29 10 Dec 2016 none non-standard — Details →
4.5.28 10 Nov 2016 none non-standard — Details →
4.5.23 11 Oct 2016 none non-standard — Details →
4.5.22 20 Sep 2016 none non-standard — Details →
4.6.38-alpha 20 Aug 2016 none non-standard — Details →
4.5.21 12 Aug 2016 none non-standard — Details →
4.5.20 12 Aug 2016 none non-standard — Details →
4.5.19 10 Aug 2016 none non-standard — Details →
4.5.18 10 Aug 2016 none non-standard — Details →
4.6.36-alpha 20 Jul 2016 none non-standard — Details →
4.5.16 18 Jul 2016 none non-standard — Details →
4.5.13 11 Jul 2016 none non-standard — Details →
4.5.10 21 Jun 2016 none non-standard — Details →
4.5.9 09 Jun 2016 none non-standard — Details →
4.6.25-alpha 06 Jun 2016 none non-standard — Details →
4.5.8 26 May 2016 none non-standard — Details →
4.5.7 26 May 2016 none non-standard — Details →
4.5.3 25 May 2016 none non-standard — Details →
4.5.0 24 May 2016 none non-standard — Details →
4.5.9-alpha 22 May 2016 none non-standard — Details →
4.5.7-alpha 22 May 2016 none non-standard — Details →
4.5.6-alpha 22 May 2016 none non-standard — Details →
4.2.1510.2205 22 Oct 2015 none non-standard — Details →
4.2.1507.118 01 Jul 2015 none non-standard — Details →
4.2.1506.2515 25 Jun 2015 none non-standard — Details →
4.2.1506.2016 20 Jun 2015 none non-standard — Details →
4.2.1502.911 09 Feb 2015 none non-standard — Details →
4.2.1409.1722 17 Sep 2014 none non-standard — Details →
4.2.1408.717 07 Aug 2014 none non-standard — Details →
4.2.1408.619 06 Aug 2014 none non-standard — Details →
4.2.1402.2112 21 Feb 2014 none non-standard — Details →
4.2.1312.1622 17 Dec 2013 none non-standard — Details →
4.2.1312.1621 16 Dec 2013 none non-standard — Details →
4.2.1312.1615 16 Dec 2013 none non-standard — Details →
4.2.1312.1416 14 Dec 2013 none non-standard — Details →
4.2.1312.1323 14 Dec 2013 none non-standard — Details →
4.2.1312.1319 13 Dec 2013 none non-standard — Details →
4.1.1311.615 18 Nov 2013 none non-standard — Details →
4.1.1309.1617 16 Sep 2013 none non-standard — Details →
4.1.1309.919 09 Sep 2013 none non-standard — Details →
4.1.1309.801 08 Sep 2013 none non-standard — Details →
4.1.1309.800 08 Sep 2013 none non-standard — Details →
4.1.1308.2321 23 Aug 2013 none — — Details →
4.1.1308.2316 23 Aug 2013 none — — Details →
4.1.1308.2120 21 Aug 2013 none — — Details →
3.1.416.3 09 Feb 2011 none — — Details →
4.0.10827 09 Feb 2011 none — — Details →
4.2.1401.2701 — none — — Details →
4.2.1408.511 — none — — Details →
4.20.0 — L1 — Yes Details →
4.20.0-alpha — none — — Details →
4.20.0-beta — none — — Details →
4.20.0-rc — L1 — Yes Details →
4.20.1 — L1 — Yes Details →
4.20.2 — none — — Details →
4.20.71 — none — — Details →
4.6.0 — none — — Details →

All 115 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for moq

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Moq v4.20.0 and 4.20.1 share hashed user data N/A low 4.20.2 10 Aug 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About moq

Is moq safe to use?

Vulert records 1 vulnerabilities for moq in NuGet: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is moq's Vulert package health score?

Vulert scores moq 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of moq affected?

No. 4.21.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of moq should I use?

4.21.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does moq have?

1 vulnerability is recorded for moq in the NuGet ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new moq vulnerabilities disclosed?

0 vulnerabilities were recorded for moq in the last 12 months, and the oldest entry in this database dates to 10 Aug 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of moq are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor moq for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the moq version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.