This vulnerability arises when pnpm, prior to versions 10.34.2 and 11.5.3, installs configDependencies declared in pnpm‑workspace.yaml before command dispatch. A repository that declares a package such as pacquet or @pnpm/pacquet as a configDependency is treated as an install‑engine opt‑in. During an install, pnpm resolves a platform‑specific binary from node_modules/.pnpm‑config/<packageName> and executes it with the permissions of the developer or CI user. Based on the description, it is inferred that the flaw, typified by CWE‑494, CWE‑78, CWE‑829, and CWE‑349, might allow a malicious binary to be executed, leading to local code execution. The impact is that any user who runs pnpm install in a workspace that contains a malicious repository can execute arbitrary code with their own privileges, potentially compromising the local system.

The affected product is pnpm, versions earlier than 10.34.2 and earlier than 11.5.3. Any project using pnpm‑workspace.yaml with repository‑controlled configDependencies to external packages is vulnerable. Developers and CI systems that automatically install dependencies from untrusted repositories are at risk.

The CVSS score of 7.5 indicates a high severity and the EPSS score of < 1% shows a low probability of exploitation at the time of this analysis. The vulnerability is not listed in the CISA KEV catalog. Based on the description, the likely attack vector is inferred to be local: the attacker must supply a repository that declares the malicious configDependency. In environments where developers or CI systems automatically install dependencies from untrusted repositories, the risk is moderate to high, warranting prompt remediation.