pnpm: Unsafe default behavior breaks integrity check

published 2026-06-25 4 mo ago modified 2026-11-03 5 d ago also GHSA-54hh-g5mx-jqcp , EUVD-2026-39489

cvss: 6.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

npm pnpm 10.34.0, 11.4.0
pnpm pnpm 10.34.0, 11.4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-50573 updated 2026-07-06 cvss 6.8

pnpm: pnpm: Package integrity check bypass allows installation of malicious content

Red Hat AMQ Broker 7 pnpm Red Hat Build of Keycloak pnpm Red Hat JBoss Enterprise Application Platform 8 pnpm Red Hat JBoss Enterprise Application Platform Expansion Pack pnpm
affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 4 mo ago (2026-06-26)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.8	CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
GitHub	3.1	6.8	CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	pnpm	<10.34.0 >=11.0.0, <11.4.0	10.34.0 11.4.0

Affected products

pnpm pnpm

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

github.com /pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp
exploit, web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-50573
advisory
github.com /pnpm/pnpm
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary