Information Exposure Affecting pnpm package, versions <11.4.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-PNPM-17769184
- published2 Jul 2026
- disclosed25 Jun 2026
Introduced: 25 Jun 2026
CVE-2026-50017 (opens in a new tab)How to fix?
Upgrade Minimos:latest pnpm to version 11.4.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pnpm package and not the pnpm package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.