pnpm binds unscoped user-level npm auth credentials to a repository-selected registry (CVE-2026-50017)
Description
pnpm versions prior to 10.34.0 and 11.4.0 can inadvertently send user-level unscoped npm authentication tokens to a registry specified 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 only sets a different registry URL without its own token. pnpm binds the user's unscoped token to the repository's registry and sends it as an Authorization header during package metadata or install operations. This behavior can expose authentication credentials to unintended registries. The issue is fixed in pnpm versions 10.34.0 and 11.4.0.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-50017 affects pnpm package manager versions prior to 10.34.0 and 11.4.0. When a user has an unscoped npm authentication token configured globally and a repository-local .npmrc file specifies a different registry URL without an auth token, pnpm mistakenly sends the user's unscoped token to the repository's registry. This occurs during normal metadata or install workflows, causing unintended credential exposure. The vulnerability is resolved in pnpm 10.34.0 and 11.4.0 by preventing the binding of user-level unscoped credentials to repository-selected registries.
Potential Impact
User-level unscoped npm authentication tokens can be leaked to registries specified by repository-local configuration files, potentially exposing sensitive credentials to unintended third-party registries. This could allow unauthorized access to private package registries if the token is accepted by the unintended registry. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade pnpm to version 10.34.0 or later, or 11.4.0 or later, where this issue is fixed. Users should ensure they are not using affected versions. No additional mitigation is indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BREW-pnpm-CVE-2026-50017
- Osv Schema Version
- 1.7.3
- Ecosystems
- ["Homebrew"]
- Cvss Version
- 4.0
Threat ID: 6ac2c0b02cdf04f656523905
Added to database: 10/04/2026, 21:10:08 UTC
Last enriched: 10/04/2026, 21:16:42 UTC
Last updated: 10/05/2026, 06:48:17 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.