pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| pnpm | pnpm | before 10.34.0; 11.0.0 to before 11.4.0 | 10.34.0, 11.4.0 | Patch available | CNA |
| — | pnpm (npm) | 11.0.0 to before 11.4.0 | 11.4.0 | Patch available | GHSA-q6j5-fjx5-2mc3 |
| — | pnpm (npm) | before 10.34.1 | 10.34.1 | Patch available | GHSA-q6j5-fjx5-2mc3 |
- pnpm Vendorpnpm Affected before 10.34.0; 11.0.0 to before 11.4.0 Fixed in 10.34.0, 11.4.0 Patch available CNA
- pnpm (npm) Vendor— Affected 11.0.0 to before 11.4.0 Fixed in 11.4.0 Patch available GHSA-q6j5-fjx5-2mc3
- pnpm (npm) Vendor— Affected before 10.34.1 Fixed in 10.34.1 Patch available GHSA-q6j5-fjx5-2mc3
Remediation
- Fix · CNA pnpm (pnpm) Fixed in 10.34.0, 11.4.0
- Fix · GHSA-q6j5-fjx5-2mc3 pnpm (npm) Fixed in 11.4.0 Advisory →
- Fix · GHSA-q6j5-fjx5-2mc3 pnpm (npm) Fixed in 10.34.1 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
Not affected: 4 products
- Red Hat AMQ Broker 7
- Red Hat Build of Keycloak
- Red Hat JBoss Enterprise Application Platform 8
- Red Hat JBoss Enterprise Application Platform Expansion Pack
Timeline
- 2026-10-02 Threatist record created from CVE-2026-50021
- 2026-10-03 Alias added: GHSA-q6j5-fjx5-2mc3
- 2026-11-03 CISA SSVC decision points changed
References
More Pnpm vulnerabilities
- TI-2025-42715 pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default" CVSS 3.1CRITICAL 9.8
- TI-2023-19086 pnpm incorrectly parses tar archives relative to specification CVSS 3.1CRITICAL 9.8
- TI-2026-40212 pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes CVSS 3.1HIGH 8.8
- TI-2026-40211 pnpm: Repository-controlled configDependencies can select a pacquet native install engine CVSS 3.1HIGH 8.8
- TI-2026-40042 pnpm: manifest identity spoof satisfies allowBuilds and runs attacker lifecycle CVSS 3.1HIGH 8.8
- TI-2026-36842 pnpm: Transitive dependency alias path traversal allows project path override via symlink replacement CVSS 3.1HIGH 8.8
Sources
- CVE-2026-50021 · CVE Program
- CVE-2026-50021 · NVD
- FIRST EPSS
- GHSA-q6j5-fjx5-2mc3 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-50021 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences