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.
References
Configurations
No configuration.
History
26 Jun 2026, 04:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/pnpm/pnpm/security/advisories/GHSA-q6j5-fjx5-2mc3 - |
25 Jun 2026, 18:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-25 18:16
Updated : 2026-06-26 05:16
NVD link : CVE-2026-50021
Mitre link : CVE-2026-50021
CVE.ORG link : CVE-2026-50021
JSON object : View
Products Affected
No product.
CWE
CWE-354
Improper Validation of Integrity Check Value
