{"id":"CVE-2026-50021","published":"2026-06-25T16:48:27Z","modified":"2026-11-03T22:13:26Z","title":"pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field","vendor":"pnpm","product":"pnpm","tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":{"score":6.8,"severity":"MEDIUM","version":"3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","provenance":"source","from":"CVE.org CNA"},"epss":{"score":0.00181,"percentile":0.07859,"provenance":"source"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"references":[{"url":"https://github.com/pnpm/pnpm/security/advisories/GHSA-q6j5-fjx5-2mc3","tags":["x_refsource_CONFIRM"]}],"priority":{"score":6.3,"factors":[{"name":"EPSS percentile","points":1.57},{"name":"CVSS severity","points":4.76}]},"vendorSlug":"pnpm","affectedVersions":[{"vendor":"pnpm","product":"pnpm","versions":["< 10.34.0",">= 11.0.0, < 11.4.0"]}],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2026-06-26T03:56:15.445797Z","from":"CISA ADP","provenance":"source"},"affected":[{"ecosystem":"npm","package":"pnpm","vulnerableRanges":[">=11.0.0, <11.4.0","<10.34.1"],"patched":["11.4.0","10.34.1"],"from":["GHSA-q6j5-fjx5-2mc3"],"provenance":"source"}],"summary":{"text":"pnpm, the Node.js package manager, has a flaw in its tarball extraction worker that skips integrity verification when a package's resolution in pnpm-lock.yaml lacks an integrity field, so installs proceed without the check that npm ci would enforce. Exploiting it requires that an attacker can both edit the lockfile to remove the integrity field and make the referenced registry URL serve altered package content, after which pnpm install --frozen-lockfile can install that tampered package without raising an integrity error.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T22:16:40Z"},"euvd":{"id":"EUVD-2026-39488","exploited":false,"provenance":"source"}}