Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. pnpm
  4. ›
  5. CVE-2026-55698

CVE-2026-55698: pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes

June 26, 2026

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.

References

  • github.com/advisories/GHSA-w466-c33r-3gjp
  • github.com/pnpm/pnpm/security/advisories/GHSA-w466-c33r-3gjp
  • nvd.nist.gov/vuln/detail/CVE-2026-55698

Code Behaviors & Features

Detect and mitigate CVE-2026-55698 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 10.34.2, all versions starting from 11.0.0 before 11.5.3

Fixed versions

  • 10.34.2
  • 11.5.3

Solution

Upgrade to versions 10.34.2, 11.5.3 or above.

Impact 8.8 HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-345: Insufficient Verification of Data Authenticity
  • CWE-494: Download of Code Without Integrity Check
  • CWE-829: Inclusion of Functionality from Untrusted Control Sphere

Source file

npm/pnpm/CVE-2026-55698.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 21 Jul 2026 00:17:57 +0000.