Pnpm
pnpm: A tarball dependency's manifest `name` escapes node_modules → arbitrary file write/overwrite on install
pnpm is a package manager. Prior to 10.34.5 and 11.11.0, pnpm accepts a scoped path traversal in a tarball dependency's package.json manifest name because pnpm11/resolving/npm-resolver/src/pickPackage.ts rejects slash characters only for unscoped names. During pnpm install, the unvalidated name reaches raw path joins in pnpm11/installing/deps-resolver/src/resolvePeers.ts, pnpm11/installing/deps-resolver/src/index.ts, and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts, causing package extraction outside node_modules and allowing attacker-controlled files to overwrite arbitrary filesystem paths even when --ignore-scripts is used. The overwrite can replace shell startup files, Git hooks, or installed package code and lead to code execution. This issue is fixed in versions 10.34.5, and 11.11.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 10.34.5
- >= 11.0.0, < 11.11.0
Fixed in 10.34.5, 11.11.0
Mitigation
Upgrade pnpm to 10.34.5 or 11.11.0 or later.
References
- Vendor advisory github.com/pnpm/pnpm/security/advisories/GHSA-…
- Patch github.com/pnpm/pnpm/pull/12872
- Patch github.com/pnpm/pnpm/pull/12890
4 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.