What’s Vulnerable › Vulnerabilities
CVE-2026-50017: pnpm binds unscoped user-level npm auth credentials to a repository-selected registry
- Severity: medium (CVSS 6.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-06-25 · updated 2026-06-30
- Weakness: CWE-200
Description
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.
Affected products
- pnpm: before 10.34.0; from 11.0.0 before 11.4.0 — fixed in 10.34.0, 11.4.0
How to fix
Upgrade to a fixed version: pnpm 10.34.0, 11.4.0. Check the vendor advisory for mitigations.
References
Get alerted when CVE-2026-50017 or the next vulnerability affects your stack