OS Command Injection Affecting pnpm package, versions <11.5.3-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.19% (9th percentile)

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-17768365
  • published2 Jul 2026
  • disclosed25 Jun 2026

Introduced: 25 Jun 2026

CVE-2026-55697  (opens in a new tab)
CWE-78  (opens in a new tab)
CWE-494  (opens in a new tab)
CWE-829  (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 install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as an install-engine opt-in. During install, pnpm resolved a platform-specific @pacquet/<platform>-<arch>/pacquet binary from node_modules/.pnpm-config/<packageName> and spawned it as the developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3.