pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes
Affects pnpmSource GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 11.5.3 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 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 18 Nov 2026.
What to do
Upgrade pnpm to 11.5.3.
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
Upgrade pnpm to version 10.34.2 or later, or 11.5.3 or later, where the vulnerability is fixed. No other mitigations are specified.
Description
A vulnerability in pnpm prior to versions 10.34.2 and 11.5.3 allows manipulation of the project environment lockfile (pnpm-lock.yaml) to bypass package-manager resolution. This can cause pnpm to install and execute arbitrary bytes during automatic version switching. The issue is fixed in versions 10.34.2 and 11.5.3.