CVE-2026-50015

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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, secondary
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's patch application pipeline (@pnpm/patch-package) performs no path validation on file paths extracted from .patch files. An attacker who contributes a malicious patch file via a pull request can write attacker-controlled content to or delete arbitrary files on the filesystem during pnpm install, as the user running the install. The diff --git header paths containing ../../ sequences traverse out of the package directory, and the traversal is difficult to catch in code review because patch file diff headers are opaque to most reviewers. This vulnerability is fixed in 10.34.0 and 11.4.0.

CVSS v3
7.3
EG Score
7.3(medium)
EPSS
18.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

Arbitrary File Write/Delete via Malicious Patch File (Path Traversal) · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-rxhj-4m44-96r4

Vendor Advisories for CVE-2026-50015(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 / 35× 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 19:47 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 07:00 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 18:35 UTCEG score recompute
  6. 2026-07-05 06:10 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 17:45 UTCEG score recompute
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 05:18 UTCEG score recompute
  11. 2026-07-03 16:51 UTCEG score recompute
  12. 2026-07-03 04:25 UTCEG score recompute
  13. 2026-07-02 16:00 UTCEG score recompute
  14. 2026-07-02 03:34 UTCEG score recompute
  15. 2026-07-01 15:09 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 02:43 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 14:18 UTCEG score recompute
  20. 2026-06-30 01:53 UTCEG score recompute
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 13:28 UTCEG score recompute
  24. 2026-06-29 01:03 UTCEG score recompute
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 10 more
  1. 2026-06-28 12:38 UTCEG score recompute
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 00:13 UTCEG score recompute
  5. 2026-06-27 11:47 UTCEG score recompute
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 23:22 UTCEG score recompute
  8. 2026-06-26 10:57 UTCEG score recompute
  9. 2026-06-25 19:50 UTCEG score recompute
  10. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50015?
CVE-2026-50015 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 patch application pipeline (@pnpm/patch-package) performs no path validation on file paths extracted from .patch files. An attacker who contributes a malicious patch file via a pull request can write attacker-controlled content to or…
When was CVE-2026-50015 disclosed?
CVE-2026-50015 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-50015 actively exploited?
CVE-2026-50015 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50015?
CVE-2026-50015 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-50015?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50015, 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-50015

Explore →

Is Your Infrastructure Affected by CVE-2026-50015?

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

Start Free Scan →Browse All CVEs