CVE-2026-50021

pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field

Published Jun 25, 2026 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

pnpm skips integrity verification when the lockfile's integrity field is absent, enabling an attacker who modifies pnpm-lock.yaml and supplies altered package content via the referenced registry to install tampered packages silently. The issue is identified by the CVE as CWE-494 and CWE-354, reflecting missing integrity checks and exception handling concerns.

Affected Systems

Environments using pnpm versions earlier than 10.34.0 or 11.4.0 are affected. The vulnerability applies to the pnpm package manager component; any project that relies on a lockfile lacking integrity fields is at risk.

Risk and Exploitability

The CVSS score of 6.8 indicates moderate risk, and the EPSS score of < 1% shows a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the attacker to modify pnpm-lock.yaml and supply a malicious package from a registry that matches the lockfile entry, then run pnpm install --frozen-lockfile. The likely attack vector involves compromised or malicious repositories or local tampering of the lockfile before installation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade pnpm to version 10.34.0 or later, or 11.4.0 or later where integrity checks are enforced.
  • Generate or validate a pnpm-lock.yaml that contains integrity fields for all dependencies before running pnpm install.
  • Avoid using --frozen-lockfile with a lockfile that may be missing integrity data; instead, run a custom validation script or use npm ci to enforce integrity checks.

Generated by OpenCVE AI on August 4, 2026 at 08:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-q6j5-fjx5-2mc3 pnpm Has an Integrity Check Bypass via Missing Lockfile Integrity Field
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Pnpm
Pnpm pnpm
Vendors & Products Pnpm
Pnpm pnpm
Type Values Removed Values Added
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.
Title pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field
Weaknesses CWE-354
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-354

    Improper Validation of Integrity Check Value

  • CWE-494

    Download of Code Without Integrity Check

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 10:13 PM
Reserved
Jun 2, 2026, 10:46 PM
Status
Analyzed
Published
Jun 25, 2026, 6:16 PM
Modified
Nov 3, 2026, 11:17 PM
Severity
Important
Public date
Jun 25, 2026, 4:48 PM