Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp
- https://github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp
FAQ
What is CVE-2026-55698?
CVE-2026-55698 is a vulnerability with a CVSS score of 8.8 (HIGH). 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 truste...
How severe is CVE-2026-55698?
CVE-2026-55698 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-55698?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.