By vendor

Pnpm vulnerabilities

Known CVEs affecting Pnpm products, prioritized by severity, with SEC.co remediation and detection guidance.

13 published vulnerabilities

• CVE-2026-50016HIGH 8.8

  pnpm, a widely-used Node.js package manager, contains a path traversal vulnerability affecting versions before 10.34.0 and 11.4.0. A malicious package published to a registry can craft dependency alias metadata containing directory traversal sequences (like '../'). When you run `pnpm install --ignore-scripts`, pnpm treats this alias as a filesystem path without proper validation, allowing the attacker's package to create symlinks that overwrite legitimate files and directories in your project with links pointing to the attacker's package folders. This means an attacker can potentially replace critical project files with their controlled content, even when you explicitly disable script execution during installation.

• CVE-2026-55698HIGH 8.8

  pnpm, a popular Node.js package manager, contains a vulnerability in versions before 10.34.2 and 11.5.3 that allows malicious repositories to inject and execute arbitrary code during package manager installation. The issue stems from pnpm's trust in cached package-manager metadata within the pnpm-lock.yaml file. When a repository commits a specially crafted lockfile with matching pnpm and @pnpm/exe versions, pnpm may skip fresh resolution of the package manager itself and instead execute code from the attacker-controlled lockfile during automatic version switching. An attacker would need to trick a developer into cloning and running commands in a malicious repository, but no special credentials or authenticated access is required.

• CVE-2026-48995HIGH 7.5

  pnpm, a widely-used Node.js package manager, fails to validate the integrity of dependencies downloaded from GitHub's codeload service before installation. An attacker who compromises codeload.github.com or intercepts traffic to it could serve malicious packages that pnpm will install without verification, even if the project's lockfile specifies different content. This occurs because pnpm does not store or check cryptographic hashes of packages from this specific source, creating a supply-chain risk for any project using pnpm to fetch dependencies from GitHub.

• CVE-2026-55487HIGH 7.5

  pnpm, a widely-used package manager, contains a vulnerability in how it normalizes package source identifiers. Before versions 10.34.2 and 11.5.3, the system would strip parenthesized text from git URLs, tarballs, file paths, and other package sources when checking if they were approved. An attacker could exploit this by crafting a malicious package source that normalizes to match an already-approved source, potentially allowing installation of unauthorized code. The vulnerability requires user interaction (such as running an install command) to trigger, but successful exploitation could grant an attacker significant control over the dependency supply chain.

• CVE-2026-55697HIGH 7.5

  pnpm, a widely-used JavaScript package manager, has a vulnerability that allows attackers to execute arbitrary code on a developer's or CI system during package installation. The vulnerability exists in how pnpm handles special dependencies declared in workspace configuration files. An attacker who controls a repository can declare a malicious package as a configuration dependency, which pnpm will then download and execute without proper safeguards. This affects pnpm versions before 10.34.2 and 11.5.3.

• CVE-2026-50015HIGH 7.3

  pnpm, a popular package manager, has a path traversal vulnerability in its patch application system that allows malicious actors to write or delete files outside the intended package directory. An attacker can exploit this by submitting a pull request with a specially crafted .patch file containing directory traversal sequences (../../). When another developer runs pnpm install, the malicious patch executes with their privileges, potentially compromising the system. The vulnerability affects versions prior to 10.34.0 and 11.4.0, where it has been patched.

• CVE-2026-55700HIGH 7.1

  pnpm, a widely-used JavaScript package manager, contains a path traversal vulnerability in its download staging feature that could allow an attacker to overwrite files outside the intended download directory. By crafting a malicious package manifest with specially designed name and version fields, an attacker could trick pnpm into writing files to unintended locations on a developer's machine. This affects versions 11.3.0 through 11.5.2. The fix validates and sanitizes both the package name and version before deriving a safe filename, then verifies the destination path before writing any files.

• CVE-2026-50021MEDIUM 6.8

  pnpm, a widely-used Node.js package manager, has a gap in its integrity verification logic. When a lockfile entry is missing an integrity checksum, pnpm will install the package without validating that its contents match what was originally locked. An attacker who can modify your lockfile and redirect package downloads to a compromised registry can inject altered code into your dependencies—even when you run pnpm install --frozen-lockfile, which is intended to be a safe, reproducible install. Unlike npm's ci command, which always enforces integrity checks, pnpm silently skips verification if the checksum is absent, creating a dangerous fail-open behavior.

• CVE-2026-50573MEDIUM 6.8

  pnpm, a widely-used Node.js package manager, has a vulnerability that undermines a core security mechanism: the lockfile integrity check. When you run `pnpm install` without the frozen flag, pnpm is supposed to verify that downloaded packages match the integrity hashes stored in pnpm-lock.yaml. However, in versions before 10.34.0 and 11.4.0, if a package registry serves modified content for a previously-locked package, pnpm reports the mismatch but then silently accepts the new content, updates the lockfile, and installs the modified package anyway. This defeats the purpose of lockfile integrity verification, which exists to prevent supply-chain attacks where registries or network intermediaries might inject malicious code into your dependencies.

• CVE-2026-50017MEDIUM 6.5

  pnpm, a widely-used Node.js package manager, has a credential leakage vulnerability that can expose your authentication tokens to unintended registries. If you use pnpm and store authentication credentials in your user-level npm configuration, a malicious or compromised repository with a local .npmrc file can trick pnpm into sending your personal authentication token to a registry of the attacker's choosing during package installation or metadata fetches. This happens because pnpm applies user-level credentials to repository-specified registries without proper validation, creating a window for credential theft.

• CVE-2026-55180MEDIUM 6.5

  pnpm, a widely-used Node.js package manager, has a credential leakage vulnerability in versions before 10.34.2 and 11.5.3. When a developer clones or installs a malicious repository, pnpm will expand environment variable placeholders (like ${API_KEY}) found in the repository's .npmrc or pnpm-workspace.yaml files. These expanded values—which may contain sensitive credentials or secrets—are then sent to an attacker-controlled package registry during dependency resolution, before any build scripts run. A developer with access to systems containing environment secrets is the attack vector; the attacker needs the victim to work with a malicious repository.

• CVE-2026-55699MEDIUM 6.5

  pnpm, a widely-used Node.js package manager, contains a path-traversal vulnerability in how it handles global package installation and removal. Specifically, malicious package manifests can specify bin names (executable entry points) that bypass pnpm's validation checks—using names like ".", "..", or empty strings. When a user installs such a package globally and later removes, updates, or adds a replacement, pnpm incorrectly derives these malicious bin names and attempts to delete files at unintended locations. A bin name of "." would target the entire global bin directory; ".." would target its parent directory. An attacker distributing a malicious package could potentially delete or corrupt critical files in the global bin environment on a user's system.

• CVE-2026-50014MEDIUM 6.4

  pnpm, a widely-used Node.js package manager, contains a command-injection vulnerability in how it processes git repository references. When pnpm resolves dependencies from git sources, it reads commit hashes from the project's lockfile. A malicious lockfile can inject git command-line options (like `--upload-pack`) in place of a legitimate commit hash. For projects using SSH or local git repositories, this allows an attacker to execute arbitrary commands during dependency installation. HTTPS-based git dependencies are not affected because the git client ignores the malicious option in that context. The vulnerability requires an attacker to control or modify the lockfile and a user to install dependencies, making it a supply-chain vector rather than a network-direct attack.