CVE-2026-55697: pnpm OS command injection via repository-controlled configDependencies

CVE-2026-55697 · Severity: high · CVSS 7.5 · Published 2026-06-25

pnpm, a popular JavaScript package manager, contains a vulnerability where a malicious project repository can trick the software into executing unauthorized native code. By including specific configuration settings in a workspace file, an attacker can force pnpm to download and run a registry-provided binary on the user's machine during routine commands like 'pnpm install'. This could allow an attacker to steal sensitive data, access private credentials, or compromise the developer's workstation or automated build systems.

Technologies: pnpm (npm). Vendors: npm, Pnpm.

Quick answers

Is CVE-2026-55697 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-55697 being exploited in the wild.
How severe is CVE-2026-55697?
High severity, with a CVSS score of 7.5, published 25 June 2026.
Which products and versions are affected?
pnpm (npm) SEMVER:introduced=0,fixed=10.34.2; Pnpm Config.Reader < 10.34.2, >= 11.0.0 < 11.5.3; Pnpm Installing.Commands < 10.34.2, >= 11.0.0 < 11.5.3.
Is there a fix for CVE-2026-55697?
Yes. pnpm (npm): upgrade to 10.34.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55697 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-55697?
Check whether you run pnpm (npm), Pnpm Config.Reader or Pnpm Installing.Commands at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • pnpm (npm): upgrade to 10.34.2 or later
    npm install pnpm@10.34.2

Technical details

A vulnerability in pnpm's handling of 'configDependencies' in 'pnpm-workspace.yaml' allows a repository to opt-in to the 'pacquet' native install engine without user consent. The vulnerability occurs because pnpm automatically installs these dependencies and treats their presence as authorization to delegate installation tasks to the resolved native binary. An attacker can provide a malicious repository that specifies 'pacquet' as a config dependency, causing pnpm to fetch a platform-specific binary from the registry and execute it via 'spawn()' in the context of the developer or CI user. The fix introduces a 'configDependencyInstallEngineAllowlist' that must be set in trusted user-level configuration (CLI, environment, or global config) to authorize such delegation.

Affected products

  • pnpm pnpm < 10.34.2, >= 11.0.0 < 11.5.3
  • pnpm @pnpm/config.reader < 10.34.2, >= 11.0.0 < 11.5.3
  • pnpm @pnpm/installing.commands < 10.34.2, >= 11.0.0 < 11.5.3

Identifiers

  • CVE-2026-55697
  • GHSA-gj8w-mvpf-x27x

Timeline

  • 2026-06-15: advisory: Initial GHSA advisory published
  • 2026-06-26: patched: Final patch and advisory update published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.