CVE-2026-50573
pnpm: Unsafe default behavior breaks integrity check
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.
INFO
Published Date :
June 25, 2026, 6:16 p.m.
Last Modified :
June 29, 2026, 9:15 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | MEDIUM | MITRE-CVE | ||||
| CVSS 3.1 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update pnpm to version 10.34.0 or later.
- Update pnpm to version 11.4.0 or later.
- Ensure lockfile integrity checks are enforced.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-50573.
| URL | Resource |
|---|---|
| https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp | Exploit Vendor Advisory |
| https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp | Exploit Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-50573 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-50573
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-50573 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-50573 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jun. 29, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N Added CPE Configuration OR *cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:node.js:*:* versions from (including) 11.0.0 up to (excluding) 11.4.0 *cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:node.js:*:* versions up to (excluding) 10.34.0 Added Reference Type GitHub, Inc.: https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp Types: Exploit, Vendor Advisory Added Reference Type CISA-ADP: https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp Types: Exploit, Vendor Advisory -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 26, 2026
Action Type Old Value New Value Changed SSVC {'id': 'CVE-2026-50573', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-06-25T17:54:41.646397Z'} {'id': 'CVE-2026-50573', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-06-25T00:00:00+00:00'} -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 25, 2026
Action Type Old Value New Value Added Reference https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp Added SSVC {'id': 'CVE-2026-50573', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-06-25T17:54:41.646397Z'} -
New CVE Received by [email protected]
Jun. 25, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'pnpm', 'product': 'pnpm', 'versions': [{'status': 'affected', 'version': '< 10.33.4'}, {'status': 'affected', 'version': '>= 11.0.0, < 11.4.0'}]}] Added 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. Added CVSS V3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Added CWE CWE-345 Added Reference https://github.com/pnpm/pnpm/security/advisories/GHSA-54hh-g5mx-jqcp