CyberRota Analysis
AI-GeneratedThe pnpm package manager is vulnerable to a path traversal issue that allows attackers to manipulate package names in the pnpm-lock.yaml file, potentially leading to arbitrary file writes outside the intended node_modules directory during installation. If lifecycle scripts are permitted, this vulnerability could enable the execution of malicious code with the user's privileges. Users of pnpm versions prior to 10.34.5 and between 11.0.0 and 11.11.0 should prioritize updating to mitigate this risk.
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 from 11.0.0 until 11.11.0, pnpm parses the package name from attacker-controlled pnpm-lock.yaml packages keys with dp.parse(depPath).name and uses it without validation in deps/graph-builder/src/lockfileToDepGraph.ts and pnpm11/deps/graph-builder/src/lockfileToDepGraph.ts. The name reaches path.join(modules, pkgName), storeController.importPackage, and pnpm11/lockfile/to-pnp/src/index.ts, allowing package contents to be written outside node_modules when a user runs pnpm install. When dangerouslyAllowAllBuilds or a matching allowBuilds entry permits lifecycle scripts, the escaped package can execute code with the user's privileges. This issue is fixed in versions 10.34.5 and 11.11.0.