CVE-2026-50573: pnpm · Unsafe default behavior breaks integrity check
Affects pnpmSource GCVE Database
Not known to be exploited · CVSS 6.8 Medium : upgrade to 11.4.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.8 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.4.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade pnpm to 11.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewpnpmpkg:brew/pnpmOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in pnpm versions 10.34.0 and 11.4.0. Users should upgrade to these versions or later to ensure the integrity check functions correctly and prevents bypass in non-frozen mode.
Description
pnpm versions prior to 10.34.0 and 11.4.0 contain a vulnerability where the package integrity check can be bypassed in non-frozen mode. This allows pnpm to accept and install altered package tarballs from the registry if they keep the same name and version, undermining lockfile integrity. The issue is fixed in versions 10.34.0 and 11.4.0.