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.2%, top 92% 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 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)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
pnpm—10.34.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 00:13 UTCEG score recompute
  3. 2026-08-24 13:09 UTCEG score recompute
  4. 2026-08-23 09:25 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 10:13 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 05:09 UTCEG score recompute
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 07:03 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 01:22 UTCEG score recompute
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 18:28 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 07:26 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 08:57 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-13 23:51 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 14:40 UTCEG score recompute
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 16:37 UTCEG score recompute
  25. 2026-08-11 05:35 UTCEG score recompute
Show 67 more
  1. 2026-08-11 00:00 UTCEPSS rescore
  2. 2026-08-09 20:22 UTCEG score recompute
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-08 22:19 UTCEG score recompute
  5. 2026-08-08 16:37 UTCEPSS rescore
  6. 2026-08-08 00:16 UTCEG score recompute
  7. 2026-08-06 15:10 UTCEG score recompute
  8. 2026-08-06 13:47 UTCEPSS rescore
  9. 2026-08-06 04:08 UTCEG score recompute
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-04 16:55 UTCEG score recompute
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 10:39 UTCEPSS rescore
  14. 2026-08-03 18:52 UTCEG score recompute
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-02 08:45 UTCEG score recompute
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-01 10:41 UTCEG score recompute
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-31 01:11 UTCEG score recompute
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 14:03 UTCEG score recompute
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-29 02:16 UTCEG score recompute
  25. 2026-07-28 15:37 UTCEPSS rescore
  26. 2026-07-28 01:06 UTCEG score recompute
  27. 2026-07-26 14:57 UTCEG score recompute
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 03:18 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-21 15:25 UTCEPSS rescore
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 14:31 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:03 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-15 02:00 UTCEPSS rescore
  43. 2026-07-13 22:31 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-13 06:13 UTCEPSS rescore
  46. 2026-07-12 05:46 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-11 08:27 UTCEPSS rescore
  49. 2026-07-09 19:10 UTCEPSS rescore
  50. 2026-07-09 19:10 UTCEPSS rescore
  51. 2026-07-08 15:16 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 02:23 UTCEPSS rescore
  55. 2026-07-05 02:30 UTCEPSS rescore
  56. 2026-07-04 06:31 UTCEPSS rescore
  57. 2026-06-30 23:22 UTCEPSS rescore
  58. 2026-06-30 11:59 UTCEG score recompute▲ 1.30
  59. 2026-06-29 21:26 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  60. 2026-06-29 14:06 UTCEPSS rescore
  61. 2026-06-29 14:06 UTCEPSS rescore
  62. 2026-06-28 14:07 UTCEPSS rescore
  63. 2026-06-28 04:56 UTCEPSS rescore
  64. 2026-06-28 04:56 UTCEPSS rescore
  65. 2026-06-27 03:08 UTCEPSS rescore
  66. 2026-06-25 19:50 UTCEG score recompute
  67. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same CWE)

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 0% probability of exploitation in the next 30 days, which ranks it in the top 92.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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