Threats Tagged 'cve-2026-50017'
View all threats tagged with 'cve-2026-50017'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-50017'
Click on any threat for detailed analysis and mitigation recommendations
0 pnpm versions prior to 10.34.0 and 11.4.0 can inadvertently send user-level unscoped npm authentication tokens to a registry specified by a repository-local .npmrc file. This occurs when the user's npm config has a default registry and an unscoped _authToken, but the repository only sets a different registry URL without its own token. pnpm binds the user's unscoped token to the repository's registry and sends it as an Authorization header during package metadata or install operations. This behavior can expose authentication credentials to unintended registries. The issue is fixed in pnpm versions 10.34.0 and 11.4.0. Join the discussion | GCVE Database | 08/13/2026, 17:28:25 UTC Added: 10/04/2026, 21:10:08 UTC |
Showing 1 to 1 of 1 result