CVE-2026-50021

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
2.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Integrity Check Bypass via Missing Lockfile Integrity Field · Advisory · pnpm/pnpm · GitHub

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

Vendor Advisories for CVE-2026-50021(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 22:36 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 11:34 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 00:31 UTCEG score recompute
  6. 2026-07-05 13:29 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:26 UTCEG score recompute
  9. 2026-07-04 15:24 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 04:23 UTCEG score recompute
  12. 2026-07-03 17:20 UTCEG score recompute
  13. 2026-07-03 06:18 UTCEG score recompute
  14. 2026-07-02 19:09 UTCEG score recompute
  15. 2026-07-02 08:06 UTCEG score recompute
  16. 2026-07-01 21:04 UTCEG score recompute
  17. 2026-07-01 10:02 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 23:00 UTCEG score recompute
  20. 2026-06-30 11:59 UTCEG score recompute▲ 1.30
  21. 2026-06-29 21:26 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 13:33 UTCEG score recompute
  25. 2026-06-28 15:10 UTCEG score recompute
Show 8 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 16:44 UTCEG score recompute
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 18:20 UTCEG score recompute
  7. 2026-06-25 19:50 UTCEG score recompute
  8. 2026-06-25 19:49 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-50021?
CVE-2026-50021 is a high vulnerability published on June 25, 2026. 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…
When was CVE-2026-50021 disclosed?
CVE-2026-50021 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50021 actively exploited?
CVE-2026-50021 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50021?
CVE-2026-50021 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-50021?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50021, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50021

Explore →

Is Your Infrastructure Affected by CVE-2026-50021?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs