CVE 6.8 MEDIUM

pnpm: Unsafe default behavior breaks integrity check_CVE-2026-50573

6.8 / 10
MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

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.

Basic Information

ID CVE-2026-50573
Source GitHub_M
Published Jun 25, 2026 at 16:50
Modified Jun 25, 2026 at 17:54

Affected Product

Vendor pnpm
Product pnpm
Version < 10.33.4
Affected Versions pnpm pnpm < 10.33.4
pnpm pnpm >= 11.0.0, < 11.4.0

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.