Medium severity6.5NVD Advisory· Published Jun 25, 2026· Updated Jun 30, 2026
CVE-2026-50017
CVE-2026-50017
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
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
pnpmnpm | < 10.34.0 | 10.34.0 |
pnpmnpm | >= 11.0.0, < 11.4.0 | 11.4.0 |
Affected products
3- Package: https://www.npmjs.com/package/pnpm
Patches
Vulnerability mechanics
References
3- github.com/pnpm/pnpm/security/advisories/GHSA-cjhr-43r9-cfmwnvdExploitVendor AdvisoryWEB
- github.com/advisories/GHSA-cjhr-43r9-cfmwghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-50017ghsaADVISORY
News mentions
1- Pnpm: Thirteen Vulnerabilities Disclosed Together, Posing Risks of ACE and Supply Chain CompromiseVypr Intelligence · Jun 25, 2026