CVE-2026-50573

published 25 Jun 2026 · updated 3 Nov 2026

pnpm: Unsafe default behavior breaks integrity check

7.8HighCVSS 6.8EPSS 0%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 10.34.0 and 11.4.0.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
pnpmpnpm<10.34.0, >=11.0.0 <11.4.010.34.0, 11.4.0
pnpm<10.33.4, >=11.0.0 <11.4.0

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-50573 severity on Zeptric[![CVE-2026-50573](https://zeptric.io/badge/cve/CVE-2026-50573.svg)](https://zeptric.io/cve/CVE-2026-50573)