CVE-2026-50014

HIGHNVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the lockfile-controlled git resolution.commit value to git fetch without a -- separator or commit-format validation. For git dependencies fetched through the shallow-fetch path, a malicious lockfile can replace the expected 40-character commit hash with a Git option such as --upload-pack=. For SSH and local transports, --upload-pack can execute the supplied command. HTTPS transports ignore --upload-pack, so the practical attack surface is primarily SSH or local git dependencies. This vulnerability is fixed in 10.34.0 and 11.4.0.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
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.
githubMentions a patch (unverified)🟡 PoC Available

Git Fetch Argument Injection via Lockfile resolution.commit · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-p4xf-rf54-rj3x

Vendor Advisories for CVE-2026-50014(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 rangeFix by version rangeDependents
pnpm—
  • every version up to 10.34.0: fixed in 10.34.0
  • 11.0.0 up to 11.4.0: fixed in 11.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:27 UTCEPSS rescore
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-23 08:44 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 07:22 UTCEG score recompute
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-14 01:18 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-12 15:46 UTCEG score recompute
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:32 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 23:20 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 01:40 UTCEG score recompute
  19. 2026-08-24 13:09 UTCEG score recompute
  20. 2026-08-23 11:13 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 10:13 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 08:05 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 07:03 UTCEG score recompute
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 01:22 UTCEG score recompute
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 16:57 UTCEG score recompute
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-16 15:41 UTCEG score recompute
  33. 2026-08-16 14:56 UTCEPSS rescore
  34. 2026-08-16 03:11 UTCEG score recompute
  35. 2026-08-16 02:14 UTCEPSS rescore
  36. 2026-08-15 02:10 UTCEG score recompute
  37. 2026-08-15 01:30 UTCEPSS rescore
  38. 2026-08-14 01:10 UTCEG score recompute
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 00:09 UTCEG score recompute
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 23:09 UTCEG score recompute
  43. 2026-08-11 10:38 UTCEG score recompute
  44. 2026-08-11 00:00 UTCEPSS rescore
  45. 2026-08-09 21:08 UTCEG score recompute
  46. 2026-08-09 13:46 UTCEPSS rescore
  47. 2026-08-08 20:08 UTCEG score recompute
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-07 19:07 UTCEG score recompute
  50. 2026-08-06 18:07 UTCEG score recompute
  51. 2026-08-06 13:47 UTCEPSS rescore
  52. 2026-08-06 05:37 UTCEG score recompute
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-04 22:13 UTCEG score recompute
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:39 UTCEPSS rescore
  57. 2026-08-03 20:21 UTCEG score recompute
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-02 05:40 UTCEG score recompute
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:40 UTCEG score recompute
  62. 2026-08-01 04:16 UTCEPSS rescore
  63. 2026-07-31 03:01 UTCEG score recompute
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 14:03 UTCEG score recompute
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-28 21:09 UTCEG score recompute
  68. 2026-07-28 15:37 UTCEPSS rescore
  69. 2026-07-27 17:17 UTCEG score recompute
  70. 2026-07-26 14:57 UTCEG score recompute
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-24 14:18 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 03:18 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50014?
CVE-2026-50014 is a high vulnerability published on June 25, 2026. pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the lockfile-controlled git resolution.commit value to git fetch without a -- separator or commit-format validation. For git dependencies fetched through the shallow-fetch path, a malicious lockfile can replace the expected…
When was CVE-2026-50014 disclosed?
CVE-2026-50014 was first published 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-50014 actively exploited?
CVE-2026-50014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50014?
CVE-2026-50014 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-50014?
A fix for CVE-2026-50014 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50014 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50014

Explore →

Is Your Infrastructure Affected by CVE-2026-50014?

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

Book a Demo →Browse All CVEs