CVE-2026-50017

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: 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 can send user-level unscoped npm authentication credentials to a registry chosen by a repository-local .npmrc file. In the reproduced case, the user's npm config contains a default registry and an unscoped _authToken. The repository does not provide a token-bearing auth line. It only sets registry= to a different registry URL. During normal pnpm metadata/install workflows, pnpm binds the user-origin unscoped credential to the repository-selected registry and sends it as an Authorization header. This vulnerability is fixed in 10.34.0 and 11.4.0.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
16.8%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
Patch available. Sources: github.
github Patch Available

pnpm binds unscoped user-level npm auth credentials to a repository-selected registry · Advisory · pnpm/pnpm · GitHub

https://github.com/pnpm/pnpm/security/advisories/GHSA-cjhr-43r9-cfmw

Vendor Advisories for CVE-2026-50017(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50017?
CVE-2026-50017 is a medium vulnerability published on June 25, 2026. pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm can send user-level unscoped npm authentication credentials to a registry chosen by a repository-local .npmrc file. In the reproduced case, the user's npm config contains a default registry and an unscoped _authToken. The repository does…
When was CVE-2026-50017 disclosed?
CVE-2026-50017 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50017 actively exploited?
CVE-2026-50017 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50017?
CVE-2026-50017 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-50017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50017, 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-50017

Explore →

Is Your Infrastructure Affected by CVE-2026-50017?

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

Start Free Scan →Browse All CVEs