Insufficient Verification of Data Authenticity Affecting pnpm package, versions <10.34.0>=11.0.0 <11.4.0


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.11% (2nd 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-JS-PNPM-17668154
  • published29 Jun 2026
  • disclosed26 Jun 2026
  • creditHuli

Introduced: 26 Jun 2026

NewCVE-2026-50573  (opens in a new tab)
CWE-345  (opens in a new tab)

How to fix?

Upgrade pnpm to version 10.34.0, 11.4.0 or higher.

Overview

pnpm is a Fast, disk space efficient package manager

Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity in the default behavior of pnpm install, which accepts tarball content that does not match the integrity value recorded in the lockfile. An attacker who controls the registry can replace the content of a previously locked package version and have it installed in place of the locked version, because on a mismatch the install reports the discrepancy, then performs automatic resolution repair, accepts the registry's new integrity, and updates the lockfile. Exploitation applies only to non-frozen installs, meaning a plain pnpm install without --frozen-lockfile, and requires the attacker to control or compromise the registry so it serves different content for an already-published version.

Workaround

This vulnerability can be avoided by running installs with --frozen-lockfile (or setting frozen-lockfile in configuration), which enforces the committed lockfile integrity and rejects content that does not match.

CVSS Base Scores

version 4.0
version 3.1