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.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w466-c33r-3gjp | pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 07 Jul 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 26 Jun 2026 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 25 Jun 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pnpm
Pnpm pnpm |
|
| Vendors & Products |
Pnpm
Pnpm pnpm |
Thu, 25 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes | |
| Weaknesses | CWE-345 CWE-494 CWE-829 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-26T03:56:12.858Z
Reserved: 2026-06-17T00:13:10.651Z
Link: CVE-2026-55698
Updated: 2026-06-26T02:09:17.743Z
No data.
OpenCVE Enrichment
Updated: 2026-06-25T22:15:04Z
Github GHSA