p PatchFirst

CVE-2026-55698

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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 8.8 · High · EPSS 0.3% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • pnpm

    Versions
    • < 10.34.2: Affected
    • >= 11.0.0, < 11.5.3: Affected

    No fix published

  • pnpm npm

    Affected ranges
    • SEMVER: < 10.34.2

    Update to 10.34.2

  • pnpm npm

    Affected ranges
    • SEMVER: ≥ 11.0.0, < 11.5.3

    Update to 11.5.3

Original sources

Check your server →