Insufficient Verification of Data Authenticity Affecting pnpm package, versions <11.5.3-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-PNPM-17770511
- published2 Jul 2026
- disclosed25 Jun 2026
Introduced: 25 Jun 2026
CVE-2026-55698 (opens in a new tab)How to fix?
Upgrade Minimos:latest pnpm to version 11.5.3-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pnpm package and not the pnpm package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.