Vulnerability in pnpm (CVE-2026-50573)
Summary
Vulnerability in pnpm (CVE-2026-50573). Confidential information can be exposed externally. Exploitable via integrity. Mitigation: upgrade to 11.4.0 or later.
Original description
The description as published by the source.
While it is unclear whether this should be classified as a vulnerability, it is being reported through this channel because the current behavior may represent an unsafe default.
Summary
pnpm install in non-frozen mode can accept new remote package content after detecting that the downloaded tarball does not match the integrity recorded in pnpm-lock.yaml.
When a package is already locked with an integrity value, and the registry later serves different metadata and tarball content for the same package name and version, pnpm initially reports an integrity mismatch. However, plain pnpm install then performs a resolution repair, accepts the registry's new integrity, updates the lockfile, installs the new content, and exits successfully.
This means the lockfile integrity check does not act as a hard stop by default.
Reproduction Scenario
- Run a local npm-compatible registry.
- Publish or serve
example-package@1.0.0with tarball contentv1. - Install it with pnpm:
pnpm add example-package@1.0.0 --registry=http://127.0.0.1:48741
- Confirm
pnpm-lock.yamlcontains thev1integrity:
packages:
example-package@1.0.0:
resolution:
integrity: sha512-...v1...
- Change the registry metadata and tarball for the same
example-package@1.0.0to contentv2. - On a clean store/cache, run:
pnpm install --registry=http://127.0.0.1:48741
Observed Behavior
pnpm detects the checksum mismatch:
WARN Got…
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-50573 has been found in pnpm.
Attackers can target a specific entry point like integrity over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade pnpm to 11.4.0 or later.
If unsure, ask your IT team or search "pnpm CVE-2026-50573" on the vendor's site.
CVE-2026-50573 (pnpm) — CWE-345 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: integrity / EINTEGRITY
Patched: 11.4.0 — 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-345) exists in pnpm. Attackers reach the vulnerable code path via integrity without authentication.
Check the vendor advisory for the affected versions of pnpm. Attack surface: integrity / EINTEGRITY.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 11.4.0.
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.4.0ステージング環境で 11.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com