pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `pnpm install` in non-frozen mode can accept new remote package content after detecting that the downloaded tarball does not match the integrity recorded in pnpm-lock.yaml. When a package is already locked with an integrity value, and the registry later serves different metadata and tarball content for the same package name and version, pnpm initially reports an integrity mismatch. However, plain pnpm install then performs a resolution repair, accepts the registry's new integrity, updates the lockfile, installs the new content, and exits successfully. This means the lockfile integrity check does not act as a hard stop by default. This vulnerability is fixed in 10.34.0 and 11.4.0.
References
| Link | Resource |
|---|---|
| https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp | Exploit Vendor Advisory |
| https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp | Exploit Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
29 Jun 2026, 21:15
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Pnpm
Pnpm pnpm |
|
| CPE | cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:node.js:*:* | |
| References | () https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp - Exploit, Vendor Advisory |
25 Jun 2026, 19:16
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp - |
25 Jun 2026, 18:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-25 18:16
Updated : 2026-06-29 21:15
NVD link : CVE-2026-50573
Mitre link : CVE-2026-50573
CVE.ORG link : CVE-2026-50573
JSON object : View
Products Affected
pnpm
- pnpm
CWE
CWE-345
Insufficient Verification of Data Authenticity
