CVE-2026-50573 pnpm: Unsafe default behavior breaks integrity check
Attackers can inject malicious code by exploiting pnpm's default behavior to bypass lockfile integrity checks during installation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-50573?
CVE-2026-50573 is a medium-severity vulnerability in pnpm, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `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. This vulnerability is fixed in 10.34.0 and 11.4.0.
Weakness: CWE-345
Which versions are affected by CVE-2026-50573?
4 open source packages ship an affected version, including pnpm. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
pnpm npm | All versions | 10.34.0 |
pnpm npm | All versions | 10.34.0 |
pnpm npm | From 11.0.0 | 11.4.0 |
pnpm npm | From 11.0.0 | 11.4.0 |
Products include Pnpm Pnpm.
How do I fix CVE-2026-50573?
Upgrade pnpm to a fixed version for your release line: 10.34.0 or 11.4.0.
Is CVE-2026-50573 being exploited?
There is no known exploitation of CVE-2026-50573 in the wild and no public exploit code.
Other vulnerabilities in pnpm
- CVE-2026-50016 pnpm: Transitive dependency alias path traversal allows project path override via symlink replacement
- CVE-2026-55698 pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes
- CVE-2025-69264 pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"
- CVE-2022-26183 Untrusted Search Path in PNPM
- CVE-2026-59195 pnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config
Sources
Also known as GHSA-54hh-g5mx-jqcp, MINI-87pc-wx5q-r933, ROOT-APP-NPM-CVE-2026-50573.