CVE-2026-50021 pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field

Medium 6.8 Published Updated

Attackers can bypass integrity checks in pnpm by removing lockfile fields, allowing installation of malicious packages during frozen installs.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-50021?

CVE-2026-50021 is a medium-severity vulnerability in pnpm, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL to serve altered package content, pnpm install --frozen-lockfile can install the altered package without an integrity error. npm's npm ci enforces integrity by default; pnpm's behavior of silently skipping verification is a pnpm-specific fail-open gap. This vulnerability is fixed in 10.34.0 and 11.4.0.

Weakness: CWE-354

Which versions are affected by CVE-2026-50021?

4 open source packages ship an affected version, including pnpm. It affects 1 product.

PackageAffectedFixed in
pnpm npmAll versions10.34.1
pnpm npmAll versions10.34.1
pnpm npmFrom 11.0.011.4.0
pnpm npmFrom 11.0.011.4.0

Products include Pnpm Pnpm.

How do I fix CVE-2026-50021?

Upgrade pnpm to a fixed version for your release line: 10.34.1 or 11.4.0.

Is CVE-2026-50021 being exploited?

There is no known exploitation of CVE-2026-50021 in the wild and no public exploit code.

Sources

Also known as GHSA-q6j5-fjx5-2mc3, MINI-5fwg-5f27-jj39, ROOT-APP-NPM-CVE-2026-50021.

Is CVE-2026-50021 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free