Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp
- https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp
FAQ
What is CVE-2026-50573?
CVE-2026-50573 is a vulnerability with a CVSS score of 6.8 (MEDIUM). 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...
How severe is CVE-2026-50573?
CVE-2026-50573 has been rated MEDIUM with a CVSS base score of 6.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-50573?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.