OS Command Injection in pnpm (CVE-2026-55697)
Summary
OS command injection in pnpm (CVE-2026-55697). Successful exploitation can lead to full system takeover. Exploitable via a93449314f398cf4bdf2e28d033c02d37395ad22. Mitigation: upgrade to 11.5.3 or later.
Original description
The description as published by the source.
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/-/pacquet binary from node_modules/.pnpm-config/ and spawned it as the developer or CI user. This vulnerability is fixed in 10.34.2 and 11.5.3.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55697 has been found in pnpm.
Attackers can target a specific entry point like a93449314f398cf4bdf2e28d033c02d37395ad22 over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade pnpm to 11.5.3 or later.
If unsure, ask your IT team or search "pnpm CVE-2026-55697" on the vendor's site.
CVE-2026-55697 (pnpm) — CWE-78 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: a93449314f398cf4bdf2e28d033c02d37395ad22 / configDependencies / pacquet / opts.runPacquet
Patched: 11.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in pnpm. Attackers reach the vulnerable code path via a93449314f398cf4bdf2e28d033c02d37395ad22 without authentication.
Check the vendor advisory for the affected versions of pnpm. Attack surface: a93449314f398cf4bdf2e28d033c02d37395ad22 / configDependencies / pacquet / opts.runPacquet.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 11.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pnpm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pnpm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pnpmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pnpm to 11.5.3ステージング環境で 11.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com