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.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
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.3Exploit: 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 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.3(medium)
EPSS
7.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

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 32× 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:19 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 09:35 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 21:02 UTCEG score recompute
  6. 2026-07-05 08:31 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 20:00 UTCEG score recompute
  9. 2026-07-04 07:30 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 19:00 UTCEG score recompute
  12. 2026-07-03 06:29 UTCEG score recompute
  13. 2026-07-02 17:59 UTCEG score recompute
  14. 2026-07-02 05:28 UTCEG score recompute
  15. 2026-07-01 16:58 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 04:28 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 15:58 UTCEG score recompute
  20. 2026-06-30 03:25 UTCEG score recompute▲ 0.90
  21. 2026-06-29 21:26 UTCNVD updateCVSS v3 → 7.3 · severity → HIGH
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 01:33 UTCEG score recompute
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 7 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 23:40 UTCEG score recompute
  4. 2026-06-27 03:08 UTCEPSS rescore
  5. 2026-06-26 21:48 UTCEG score recompute
  6. 2026-06-25 19:50 UTCEG score recompute
  7. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(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 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-50014 actively exploited?
CVE-2026-50014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50014, 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-50014

Explore →

Is Your Infrastructure Affected by CVE-2026-50014?

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

Start Free Scan →Browse All CVEs