Impact
The vulnerability arises when pnpm passes a lockfile-controlled git resolution.commit value directly to the git fetch command without any separator or validation. A malicious lockfile can replace the expected 40‑character commit SHA with a git option such as --upload-pack=<command>. When the dependency is fetched over SSH or via a local path, the injected --upload-pack option is executed, allowing an attacker to run arbitrary shell commands on the host that executes pnpm. This is a form of command injection (CWE-78).
Affected Systems
pnpm package managers older than 10.34.0 or 11.4.0 are affected. Only the pnpm product is listed by the CNA.
Risk and Exploitability
The CVSS v3.1 score of 6.4 indicates moderate severity. The EPSS score of less than 1% shows exploitation likelihood is very low. The issue is not listed in the CISA KEV catalog. Exploitation requires a crafted lockfile processed during a pnpm install. If the lockfile references a git repository via SSH or a local path and the attacker supplies an --upload-pack option, the command is executed with the permissions of the pnpm process, allowing arbitrary code execution.
OpenCVE Enrichment
Github GHSA