Vulnerability · Published Jun 25, 2026 · Assigned by GitHub_M
CVE-2026-50021pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field
Medium 6.8
In plain English
A medium-severity security flaw in pnpm from pnpm. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | pnpm | 11.4.0 | GHSA-q6j5-fjx5-2mc3 |
| npm | pnpm | 10.34.1 | GHSA-q6j5-fjx5-2mc3 |
Affected products (as reported)
Weakness: CWE-354 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
References
- https://github.com/pnpm/pnpm/security/advisories/GHSA-q6j5-fjx5-2mc3 x_refsource_CONFIRM