pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persist package-manager bootstrap metadata in the first YAML document of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an already resolved packageManagerDependencies entry when the committed env lockfile contained matching pnpm and @pnpm/exe versions. A malicious repository could therefore commit package-manager lockfile package records and snapshots that bypassed fresh package-manager resolution, then cause pnpm to install and execute bytes selected by that committed lockfile state during automatic version switching. This vulnerability is fixed in 10.34.2 and 11.5.3.
References
| Link | Resource |
|---|---|
| https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp | Exploit Vendor Advisory |
| https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp | Exploit Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-06-25 18:16
Updated : 2026-06-30 19:03
NVD link : CVE-2026-55698
Mitre link : CVE-2026-55698
CVE.ORG link : CVE-2026-55698
JSON object : View
Products Affected
pnpm
- pnpm
