CVE-2026-50017: pnpm binds unscoped user-level npm auth credentials to a repository-selected registry
Affects pnpmSource GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 11.4.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade pnpm to 11.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewpnpmpkg:brew/pnpmOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
An official fix is available in pnpm versions 10.34.0 and 11.4.0. Users should upgrade to these versions or later to prevent unintentional exposure of npm authentication tokens. Until upgraded, users should review their npm and repository .npmrc configurations to avoid scenarios where an unscoped token is sent to a repository-specified registry without its own token.
Description
pnpm versions prior to 10.34.0 and 11.4.0 can unintentionally send user-level unscoped npm authentication tokens to a registry specified only by a repository-local .npmrc file. This occurs when the user's npm config has a default registry and an unscoped _authToken, but the repository sets a different registry URL without its own token. As a result, the user's token is bound to the repository's registry and sent as an Authorization header during package operations, potentially exposing credentials to unintended registries. The issue is fixed in pnpm versions 10.34.0 and 11.4.0.