Vulnerability Database · npm · jpv · Version
jpv 2.2.1
2.2.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.1.2.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 19 Apr 2020
Licence ISC
Also known from other sources 1
Newer releases 28
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
jpv 2.2.1 vulnerabilities
1 vulnerability cover jpv 2.2.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-17479: Validation bypass in jpv | 9.8 critical | 2.2.2 | 06 May 2021 |
Looking for another version, or everything Vulert holds for jpv?
Questions
About jpv 2.2.1
Is jpv 2.2.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover jpv 2.2.1: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 3.1.2, and each entry above names the fixed version to move to.
Which version of jpv should I use instead of 2.2.1?
3.1.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.2.1 the latest release of jpv?
No. 2.2.1 was published 19 Apr 2020, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor jpv for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jpv version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.