Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. pnpm
  4. ›
  5. CVE-2026-50021

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

June 26, 2026

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.

References

  • github.com/advisories/GHSA-q6j5-fjx5-2mc3
  • github.com/pnpm/pnpm/security/advisories/GHSA-q6j5-fjx5-2mc3
  • nvd.nist.gov/vuln/detail/CVE-2026-50021

Code Behaviors & Features

Detect and mitigate CVE-2026-50021 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 10.34.1, all versions starting from 11.0.0 before 11.4.0

Fixed versions

  • 10.34.1
  • 11.4.0

Solution

Upgrade to versions 10.34.1, 11.4.0 or above.

Impact 6.8 MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Learn more about CVSS

Weakness

  • CWE-354: Improper Validation of Integrity Check Value

Source file

npm/pnpm/CVE-2026-50021.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Thu, 16 Jul 2026 00:18:24 +0000.