CVE-2026-50573: pnpm Silent Supply-Chain Integrity Bypass in Versions <10.34.0 and <11.4.0

Technical summary

The vulnerability exists in pnpm's integrity validation logic during non-frozen installation mode. When pnpm detects that a downloaded tarball's hash does not match the integrity value in pnpm-lock.yaml, the expected behavior is to fail the operation and alert the user. Instead, the affected versions invoke a resolution repair process that silently accepts the new integrity hash from the registry, overwrites the lockfile, and proceeds with installation. This occurs because the integrity check is not treated as a hard stop; rather, it triggers automatic remediation that trusts the registry's new metadata. The fix in 10.34.0 and 11.4.0 hardens this validation to reject mismatches by default unless explicitly overridden by the user.

Business impact

For development teams, this vulnerability creates a window for supply-chain compromise without obvious detection. An attacker who can intercept or manipulate registry responses (via DNS hijacking, BGP hijacking, compromised registry, or insider access) could inject malicious code into dependencies that would be silently accepted and installed by any team member running `pnpm install` on an existing project. The silent acceptance and lockfile update makes the compromise difficult to detect in code review or CI/CD logs, since no error is raised. Organizations relying on lockfile integrity as a security boundary should treat this as a medium-priority remediation to prevent supply-chain attacks.

Affected systems

pnpm versions prior to 10.34.0 (in the 10.x line) and prior to 11.4.0 (in the 11.x line) are vulnerable. Any project using an affected version of pnpm that runs `pnpm install` without the --frozen-lockfile flag is at risk. The --frozen-lockfile flag, when used, provides protection by refusing to modify the lockfile and failing if integrity mismatches are detected, so projects already using that flag are not exploitable via this mechanism.

Exploitability

Exploitation requires two conditions: the attacker must be able to manipulate or intercept package registry responses, and a developer must run `pnpm install` (not `pnpm install --frozen-lockfile`) on a project with an existing lockfile. The CVSS vector AV:N/AC:H/UI:R reflects that this is network-accessible but requires moderate complexity (registry manipulation) and user interaction (running install). The attack is not trivial but is within reach of sophisticated threat actors with registry access or network position.

Remediation

Upgrade pnpm to 10.34.0 or later if using the 10.x line, or 11.4.0 or later if using the 11.x line. Additionally, organizations should adopt the practice of running `pnpm install --frozen-lockfile` in CI/CD pipelines and development workflows wherever possible, which enforces strict lockfile verification and prevents silent acceptance of new content.

Patch guidance

Apply the vendor patch by upgrading pnpm: use `npm install -g [email protected]` for the 10.x line or `npm install -g [email protected]` for the 11.x line, or the latest version available. Verify the upgrade using `pnpm --version`. After patching, re-run `pnpm install` to ensure your lockfile is consistent with the patched behavior. No lockfile migration is required; the patch is backward-compatible.

Detection guidance

Monitor for unexpected changes to pnpm-lock.yaml files, especially integrity hash changes that lack corresponding code review comments or ticket references. Enable audit logging on npm registry proxies and mirrors to detect unusual integrity value changes. In CI/CD, configure pre-commit hooks to validate that lockfile integrity hashes have not drifted without explicit developer approval. Review logs for any `pnpm install` executions that result in lockfile modifications in production or release pipelines.

Why prioritize this

Although this is rated MEDIUM severity, it should be prioritized based on your supply-chain security posture. If your organization treats lockfile integrity as a security control (which it should), this vulnerability directly undermines that control and warrants swift patching. Teams already using `--frozen-lockfile` in all automated contexts face reduced risk but should still upgrade to close the gap for manual developer installs.

Risk score, explained

The CVSS 3.1 score of 6.8 (MEDIUM) reflects high confidentiality and integrity impact (an attacker can inject arbitrary code) but requires network attacker positioning (AC:H) and user interaction (UI:R) to exploit. The score does not account for the widespread use of pnpm in JavaScript ecosystems or the difficulty of detecting silent supply-chain manipulation, factors that elevate business risk even if technical exploitability is moderate.

Frequently asked questions