PT-2026-52523

CVE-2026-55698

·

Published

2026-06-25

·

Updated

2026-07-30

Description by

CVSS 3.1
8.8
High
MetricsAV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions pnpm versions prior to 10.34.2 pnpm versions 11.0.0 through 11.5.2
Description pnpm can persist package-manager bootstrap metadata in the first YAML document of the pnpm-lock.yaml file. The issue occurs when pnpm incorrectly trusts an already resolved packageManagerDependencies entry if the committed environment lockfile contains matching pnpm and @pnpm/exe versions. This trust failure during automatic version switching allows a malicious repository to commit crafted lockfile package records and snapshots that bypass fresh package-manager resolution.
An attacker can exploit this by committing a crafted pnpm-lock.yaml file. When a victim runs pnpm in that repository with auto-switching enabled, pnpm may install and execute attacker-selected bytes. This can lead to arbitrary code execution with the privileges of the user, potentially compromising developer workstations and CI runners.
Technical details include the following:
  • API Endpoints: Not applicable.
  • Vulnerable Parameters or Variables: packageManagerDependencies within the pnpm-lock.yaml file.
  • Function Names: switchCliVersion() and resolvePackageManagerIntegrities().
Recommendations Upgrade pnpm to version 10.34.2. Upgrade pnpm to version 11.5.3.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
GHSA-W466-C33R-3GJP
Found an issue in the description? Have something to add? Feel free to write us 👾