Back

HIGH

pnpm: Repository-controlled configDependencies can select a pacquet native install engine

Published Jun 25, 2026

Description

pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as an install-engine opt-in. During install, pnpm resolved a platform-specific @pacquet/<platform>-<arch>/pacquet binary from node_modules/.pnpm-config/<packageName> and spawned it as the developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3.

Affected products

Remediation

Red Hat statement

This is an Important arbitrary code execution flaw in pnpm, a package manager. A remote attacker could exploit this by crafting a malicious repository that, when used by a developer or CI system, leads to the execution of a malicious binary. This vulnerability arises from pnpm's improper handling of `configDependencies` declared in `pnpm-workspace.yaml`, allowing an untrusted repository to opt into a native install engine.

References (6)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner GitHub_M
Published Jun 25, 2026
Updated Jun 29, 2026
Reserved Jun 17, 2026
CISA Vulnrichment
Updated Jun 26, 2026
NVD
Status Analyzed
Modified Jun 30, 2026
Red Hat
Severity Important
Public date Jun 25, 2026
GHSA-GJ8W-MVPF-X27X