Vulnerability in Pnpm

CVE-2026-50573

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 6.8 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N.

EPSS exploit prediction

EPSS: 0.002 (5.4th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 5th percentile — 5.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-50573: held from 0.002 to 0.002.

EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000

Affected products

  • Pnpm — versions < 10.33.4, >= 11.0.0, < 11.4.0

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-50573?
CVE-2026-50573 is a medium-severity vulnerability in Pnpm, classified under Insufficient Verification of Data Authenticity. CVSS score: 6.8/10. Published 2026-06-25.
How severe is CVE-2026-50573?
Medium severity. CVSS v3 base score is 6.8 out of 10.