Skip to content
OpenAdvisories
Medium · 6.8 CVE-2026-50021 EUVD-2026-39488GHSA-q6j5-fjx5-2mc3

pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field

Published Jun 25, 2026 · Updated Nov 3, 2026 · Assigned by GitHub_M

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

VendorProductAffectedFixed
pnpm pnpm < 10.34.0, >= 11.0.0, < 11.4.0 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling pnpm-stage0 No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
npm pnpm >= 11.0.0, < 11.4.0 11.4.0 GHSA-q6j5-fjx5-2mc3
npm pnpm < 10.34.1 10.34.1 GHSA-q6j5-fjx5-2mc3

References