CVE-2026-55698 pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes
HighCVSS 8.8
EPSS 0.30%
- Published
- Updated
- Exploit status
- No public exploit known
Description
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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| pnpm | = < 10.34.2 | No fix listed |
| pnpm | = >= 11.0.0, < 11.5.3 | No fix listed |
| npm pnpm(npm) | < 10.34.2 | 10.34.2 |
| npm pnpm(npm) | >= 11.0.0, < 11.5.3 | 11.5.3 |
| pnpm | < 10.34.2 | 10.34.2 |
| pnpm | >= 11.0.0, < 11.5.3 | 11.5.3 |
References
- https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp exploit vendor-advisory
- Red Hat CVE page vendor-advisory
- Red Hat Bugzilla 2493022 issue-tracking
- www.cve.org
- nvd.nist.gov third-party-advisory
- github.com