Improper Validation of Integrity Check Value Affecting pnpm package, versions <11.4.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-PNPM-17741623
- published1 Jul 2026
- disclosed25 Jun 2026
Introduced: 25 Jun 2026
CVE-2026-50021 (opens in a new tab)How to fix?
Upgrade Minimos:latest pnpm to version 11.4.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pnpm package and not the pnpm package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL to serve altered package content, pnpm install --frozen-lockfile can install the altered package without an integrity error. npm's npm ci enforces integrity by default; pnpm's behavior of silently skipping verification is a pnpm-specific fail-open gap. This vulnerability is fixed in 10.34.0 and 11.4.0.