Vulnerability · Published Jun 25, 2026 · Assigned by GitHub_M
CVE-2026-50017pnpm binds unscoped user-level npm auth credentials to a repository-selected registry
Medium 6.9
In plain English
A medium-severity information exposure in pnpm from pnpm. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 38% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | pnpm | 10.34.0 | GHSA-cjhr-43r9-cfmw |
| npm | pnpm | 11.4.0 | GHSA-cjhr-43r9-cfmw |
Affected products (as reported)
Weakness: CWE-200, CWE-522 · Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
References
- https://github.com/pnpm/pnpm/security/advisories/GHSA-cjhr-43r9-cfmw x_refsource_CONFIRM