CVE-2026-50021: pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field

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-354

Description

pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL to serve altered package content, pnpm install --frozen-lockfile can install the altered package without an integrity error. npm's npm ci enforces integrity by default; pnpm's behavior of silently skipping verification is a pnpm-specific fail-open gap. 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-50021 or the next vulnerability affects your stack