Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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.
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 applicationsUpgrade pnpm to version 10.34.0, 11.4.0 or higher.
pnpm is a Fast, disk space efficient package manager
Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the config and auth-header flow, which binds unscoped user-level npm _authToken credentials to whatever default registry a repository-local .npmrc selects. An attacker can capture a developer's or CI job's user-level npm token by publishing a repository whose .npmrc sets registry= to an attacker-controlled endpoint, to which pnpm then sends the unscoped default credentials during pnpm install, pnpm view, or similar metadata commands. The target must have unscoped user-level credentials in their global npm configuration, the disclosure is limited to those default tokens while URL-scoped tokens for other registries are not exposed, and the leak occurs before any lifecycle scripts run so it does not require package code execution.
This vulnerability can be avoided by storing npm credentials as URL-scoped tokens, such as //registry.npmjs.org/:_authToken=..., rather than an unscoped default _authToken, since registry-scoped credentials are not sent to a registry selected by a repository's .npmrc.