Vulnerability in pnpm (CVE-2026-55487)
Summary
Vulnerability in pnpm (CVE-2026-55487). Successful exploitation can lead to full system takeover. Exploitable via bf1b731ee6. Mitigation: upgrade to 10.34.2 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, the generic peer-suffix normalizer also stripped parenthesized text from git, URL, tarball, file, and other opaque locators. Approval for one source string could therefore authorize a different attacker-controlled source whose locator normalized to the same value. 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-55487 has been found in pnpm.
Attackers can target a specific entry point like bf1b731ee6 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 10.34.2 or later.
If unsure, ask your IT team or search "pnpm CVE-2026-55487" on the vendor's site.
CVE-2026-55487 (pnpm) — CWE-346 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: bf1b731ee6 / allowBuilds / pnpm
Patched: 10.34.2 — 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.
A vulnerability (CWE-346) exists in pnpm. Attackers reach the vulnerable code path via bf1b731ee6 without authentication.
Check the vendor advisory for the affected versions of pnpm. Attack surface: bf1b731ee6 / allowBuilds / pnpm.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 10.34.2.
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 10.34.2ステージング環境で 10.34.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com
- web github.com