CVE-2026-50573: pnpm: Unsafe default behavior breaks integrity check

Severity: high (CVSS 8.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-06-25 · updated 2026-06-29
Weakness: CWE-345

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.

Affected products

pnpm: before 10.34.0; from 11.0.0 before 11.4.0 — fixed in 10.34.0, 11.4.0

How to fix

Upgrade to a fixed version: pnpm 10.34.0, 11.4.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-50573 or the next vulnerability affects your stack