How severe is CVE-2026-50021?

CVE-2026-50021 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-50021 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-50021?

CVE-2026-50021 affects Pnpm. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-50021?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-50021 have an EU (EUVD) identifier?

Yes. CVE-2026-50021 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39488.

When was CVE-2026-50021 published?

CVE-2026-50021 was published on 2026-06-25 and last updated on 2026-06-29.

CVE-2026-50021

CVE-2026-50021 is a medium-severity vulnerability in Pnpm with a CVSS 3.x base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-354.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-39488
Weakness: CWE-354
Affected product: Pnpm
Published: 2026-06-25
Last modified: 2026-06-29

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.

Frequently asked questions

What is CVE-2026-50021?: 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.
How severe is CVE-2026-50021?: CVE-2026-50021 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-50021 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-50021?: CVE-2026-50021 affects Pnpm. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-50021?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-50021 have an EU (EUVD) identifier?: Yes. CVE-2026-50021 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39488.
When was CVE-2026-50021 published?: CVE-2026-50021 was published on 2026-06-25 and last updated on 2026-06-29.

References

https://github.com/pnpm/pnpm/security/advisories/GHSA-q6j5-fjx5-2mc3

Affected products (1)

cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:node.js:*:*

More vulnerabilities in Pnpm

CVE-2024-53866 — Critical (CVSS 9.8): The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one…
CVE-2026-55698 — High (CVSS 8.8): pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persist package-manager bootstrap metadata in the…
CVE-2026-50016 — High (CVSS 8.8): pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm allows a transitive dependency alias from registry package…
CVE-2025-69264 — High (CVSS 8.8): pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during…
CVE-2022-26183 — High (CVSS 8.8): PNPM v6.15.1 and below was discovered to contain an untrusted search path which causes the application to behave in…
CVE-2026-59195 — High (CVSS 8.2): pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile…

All CVEs affecting Pnpm →

Other CWE-354 vulnerabilities

CVE-2025-11543 — Critical (CVSS 9.8): Improper Validation of Integrity Check Value vulnerability in Sharp Display Solutions projectors allows a attacker may…
CVE-2024-25678 — Critical (CVSS 9.8): In LiteSpeed QUIC (LSQUIC) Library before 4.0.4, DCID validation is mishandled.
CVE-2023-33668 — Critical (CVSS 9.8): DigiExam up to v14.0.2 lacks integrity checks for native modules, allowing attackers to access PII and takeover…
CVE-2017-15994 — Critical (CVSS 9.8): rsync 3.1.3-development before 2017-10-24 mishandles archaic checksums, which makes it easier for remote attackers to…
CVE-2026-49230 — Critical (CVSS 9.1): Improper Validation of Integrity Check Value vulnerability in Apache APISIX. The jwe-decrypt plugin under default…
CVE-2026-34182 — Critical (CVSS 9.1): Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the…

Browse all CWE-354 vulnerabilities →