Skip to main content
VulnerabilityPublished Updated

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

Affects pnpmSource GCVE Database

0
Compare
Authoritative record:CVE-2026-50021· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : upgrade to 11.4.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.8
EPSS
0.1% chance of exploitation in 30 days – higher than 7% 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:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Upgrade pnpm to 11.4.0.

Affected software

ProductAffectedFixed in
Homebrewpnpmpkg:brew/pnpmOther threatsAffected
  • >=4.0.2 <11.4.0
Fixed in
  • 11.4.0

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 or later versions to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the official patch.

Description

A vulnerability in pnpm before versions 10.34.0 and 11.4.0 allows bypassing integrity checks during package installation if the integrity field is missing from the lockfile. This can lead to installation of altered packages without detection when using the --frozen-lockfile option. The issue is specific to pnpm and differs from npm's default integrity enforcement. The vulnerability is fixed in versions 10.34.0 and 11.4.0.

References

Community reviews

Loading reviews…