VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

convict: vulnerability history, versions and safety

convict is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 63 releases, from Apr 2022 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C3 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 26 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all convict vulnerabilities

Vulert verdict on convict 6.2.5 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 6.2.5 — unaffected i
  • Vulnerabilities on record 5 over 3 years · 2 in the last year i
  • Latest disclosure 26 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1,006 packages i
  • Stars 2,376 i
  • OpenSSF scorecard 1/10 i
  • Last release 7 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, 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 convict, 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
6.2.5 19 Mar 2026 none Apache-2.0 — Details →
6.2.4 07 Jan 2023 C2 Apache-2.0 Yes Details →
6.2.3 07 May 2022 C2 H1 Apache-2.0 Yes Details →
6.2.2 27 Mar 2022 C3 H2 Apache-2.0 Yes Details →
6.2.1 20 Oct 2021 C3 H2 Apache-2.0 Yes Details →
5.2.1 23 Jul 2021 C3 H2 Apache-2.0 Yes Details →
6.2.0 15 Jul 2021 C3 H2 Apache-2.0 Yes Details →
6.1.0 03 May 2021 C3 H2 Apache-2.0 Yes Details →
6.0.1 11 Mar 2021 C3 H2 Apache-2.0 Yes Details →
6.0.0 08 May 2020 C3 H2 Apache-2.0 Yes Details →
5.2.0 14 Oct 2019 C3 H2 Apache-2.0 Yes Details →
5.1.0 26 Jul 2019 C3 H2 Apache-2.0 Yes Details →
5.0.0 06 May 2019 C3 H2 Apache-2.0 Yes Details →
4.4.1 17 Dec 2018 C3 H2 Apache-2.0 Yes Details →
4.4.0 23 Sep 2018 C3 H2 Apache-2.0 Yes Details →
4.3.2 19 Jul 2018 C3 H2 Apache-2.0 Yes Details →
4.3.1 28 Jun 2018 C3 H2 Apache-2.0 Yes Details →
4.3.0 04 Jun 2018 C3 H2 Apache-2.0 Yes Details →
4.2.0 23 Mar 2018 C3 H2 Apache-2.0 Yes Details →
4.1.0 16 Mar 2018 C3 H2 Apache-2.0 Yes Details →
4.0.2 30 Nov 2017 C3 H2 Apache-2.0 Yes Details →
4.0.1 29 Sep 2017 C3 H2 Apache-2.0 Yes Details →
4.0.0 22 Jun 2017 C3 H2 Apache-2.0 Yes Details →
3.0.0 22 Mar 2017 C3 H2 Apache-2.0 Yes Details →
2.0.0 24 Dec 2016 C3 H2 Apache-2.0 Yes Details →
1.5.0 28 Sep 2016 C3 H2 Apache-2.0 Yes Details →
1.4.0 30 May 2016 C3 H2 Apache-2.0 Yes Details →
1.3.0 14 Apr 2016 C3 H2 Apache-2.0 Yes Details →
1.2.0 01 Apr 2016 C3 H2 Apache-2.0 Yes Details →
1.1.3 18 Mar 2016 C3 H2 Apache-2.0 Yes Details →
1.1.2 12 Feb 2016 C3 H2 Apache-2.0 Yes Details →
1.1.1 12 Feb 2016 C3 H2 Apache-2.0 Yes Details →
1.1.0 12 Feb 2016 C3 H2 Apache-2.0 Yes Details →
1.0.2 09 Dec 2015 C3 H2 Apache-2.0 Yes Details →
1.0.1 11 Aug 2015 C3 H2 Apache-2.0 Yes Details →
1.0.0 02 Aug 2015 C3 H2 Apache-2.0 Yes Details →
0.8.2 20 Jul 2015 C3 H2 Apache-2.0 Yes Details →
0.8.1 20 Jul 2015 C3 H2 Apache-2.0 Yes Details →
0.8.0 01 Jun 2015 C3 H2 Apache-2.0 Yes Details →
0.7.0 29 Apr 2015 C3 H2 Apache-2.0 Yes Details →
0.6.1 12 Jan 2015 C3 H2 Apache-2.0 Yes Details →
0.6.0 13 Nov 2014 C3 H2 Apache-2.0 Yes Details →
0.5.1 29 Oct 2014 C3 H2 Apache-2.0 Yes Details →
0.5.0 15 Oct 2014 C3 H2 Apache-2.0 Yes Details →
0.4.3 13 Oct 2014 C3 H2 Apache-2.0 Yes Details →
0.4.2 12 Jan 2014 C3 H2 Apache-2.0 Yes Details →
0.4.1 14 Oct 2013 C3 H2 Apache-2.0 Yes Details →
0.4.0 31 Jul 2013 C3 H2 Apache-2.0 Yes Details →
0.3.3 17 Jun 2013 C3 H2 Apache-2.0 Yes Details →
0.3.2 08 Jun 2013 C3 H2 Apache-2.0 Yes Details →
0.3.1 04 Jun 2013 C3 H2 Apache-2.0 Yes Details →
0.3.0 03 Jun 2013 C3 H2 Apache-2.0 Yes Details →
0.2.3 27 May 2013 C3 H2 Apache-2.0 Yes Details →
0.2.2 25 May 2013 C3 H2 Apache-2.0 Yes Details →
0.2.1 25 May 2013 C3 H2 Apache-2.0 Yes Details →
0.2.0 23 May 2013 C3 H2 Apache-2.0 Yes Details →
0.1.1 20 May 2013 C3 H2 Apache-2.0 Yes Details →
0.1.0 05 Mar 2013 C3 H2 Apache-2.0 Yes Details →
0.0.6 30 Jan 2012 C3 H2 Apache-2.0 Yes Details →
0.0.5 27 Jan 2012 C3 H2 Apache-2.0 Yes Details →
0.0.4 27 Jan 2012 C3 H2 Apache-2.0 Yes Details →
0.0.3 26 Jan 2012 C3 H2 Apache-2.0 Yes Details →
0.0.2 22 Jan 2012 C3 H2 Apache-2.0 Yes Details →
0.0.1 22 Jan 2012 C3 H2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for convict

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-21190: Prototype Pollution in convict 9.8 critical 6.2.3 14 May 2022
CVE-2026-33864: Convict Package Prototype Pollution Vulnerability 9.4 critical 6.2.5 26 Mar 2026
CVE-2026-33863: Convict Prototype Pollution Vulnerability 9.4 critical 6.2.5 26 Mar 2026
CVE-2022-22143: Prototype Pollution in convict 8.4 high 6.2.3 20 Apr 2022
CVE-2023-0163: Prototype Pollution in convict 8.4 high 6.2.4 10 Jan 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 convict

Is convict safe to use?

Vulert records 5 vulnerabilities for convict in npm: 3 critical, 2 high, 0 medium and 0 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 convict's Vulert package health score?

Vulert scores convict 69/100, which reads as usable, but worth attention. 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 convict affected?

No. 6.2.5, 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 convict should I use?

6.2.5 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 convict have?

5 vulnerabilities are recorded for convict in the npm ecosystem: 3 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new convict vulnerabilities disclosed?

2 vulnerabilities were recorded for convict in the last 12 months, and the oldest entry in this database dates to 20 Apr 2022. 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 convict 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 convict for upcoming vulnerabilities?

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