CVE-2021-43616The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json…
- 9.0CriticalCVSS base score
- 2.6%Exploitation in 30 daysEPSS · top 14% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.
Timeline
Published
- 3 years later
· 3 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| mitreCNA (assigner) | 3.1 | Critical9.0 | CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N |
| NVDNVD · Modified | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 2.6% · top 14% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.0.
Affected products
n/a
- affected n/a
References
References10
- https://github.com/npm/cli/issues/2701 (opens in a new tab)x_transferred
- https://docs.npmjs.com/cli/v7/commands/npm-ci (opens in a new tab)x_transferred
- https://github.com/icatalina/CVE-2021-43616 (opens in a new tab)x_transferred
- https://medium.com/cider-sec/this-time-we-were-lucky-85c0dcac94a0 (opens in a new tab)x_transferred
- https://security.netapp.com/advisory/ntap-20211210-0002/ (opens in a new tab)x_transferred
- https://github.com/npm/cli/commit/457e0ae61bbc55846f5af44afa4066921923490f (opens in a new tab)x_transferred
- FEDORA-2022-97b214b298 (opens in a new tab)vendor-advisoryx_transferred
- https://docs.npmjs.com/cli/v8/commands/npm-ci (opens in a new tab)x_transferred
- https://github.com/npm/cli/issues/2701#issuecomment-979054224 (opens in a new tab)x_transferred
- https://github.com/npm/cli/issues/2701#issuecomment-972900511 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-30530 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-43616)Record last updated .