CyberRota Analysis
AI-GeneratedThe pnpm package manager is vulnerable to a scoped path traversal issue that allows attacker-controlled files to overwrite arbitrary filesystem paths during the installation of tarball dependencies, even with the --ignore-scripts option enabled. This can lead to critical security risks, including potential code execution through the replacement of sensitive files such as shell startup scripts or Git hooks. Users of pnpm, particularly those managing sensitive environments or critical applications, should prioritize upgrading to versions 10.34.5 or 11.11.0 to mitigate this vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.