pnpm: Path traversal
Affects pnpmSource GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 11.8.0 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.8.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:LExploitation 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 16 Nov 2026.
What to do
Upgrade pnpm to 11.8.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.4 and 11.8.0. Users should upgrade to at least these versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
pnpm versions prior to 10.34.4 and 11.8.0 have a path traversal vulnerability in the configDependencies environment lockfile feature. This flaw allows a crafted pnpm-lock.yaml file to cause symlink creation outside the intended node_modules/.pnpm-config directory during installation, potentially leading to unauthorized symlink creation and integrity issues. The vulnerability is fixed in versions 10.34.4 and 11.8.0.