Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

npm-lockfile vulnerabilities and fixes

Recent CVEs affecting npm-lockfile, with upgrade or downgrade steps. 1 tracked.

Also searched as: npm lockfile.

npm-lockfile has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-03-03. Highest priority: CVE-2022-0841 (score 65/100).

FAQ

How do I fix npm-lockfile vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is npm-lockfile being exploited right now?

None of the tracked npm-lockfile CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which npm-lockfile CVE should I patch first?

CVE-2022-0841 currently ranks highest (65/100): OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4..

← Back to latest CVEs