Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. pnpm
  4. ›
  5. CVE-2026-50017

CVE-2026-50017: pnpm binds unscoped user-level npm auth credentials to a repository-selected registry

June 26, 2026

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 was reproduced with fake credentials and loopback registries only. No third-party registry or real token was used.

References

  • github.com/advisories/GHSA-cjhr-43r9-cfmw
  • github.com/pnpm/pnpm/security/advisories/GHSA-cjhr-43r9-cfmw
  • nvd.nist.gov/vuln/detail/CVE-2026-50017

Code Behaviors & Features

Detect and mitigate CVE-2026-50017 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 10.34.0, all versions starting from 11.0.0 before 11.4.0

Fixed versions

  • 10.34.0
  • 11.4.0

Solution

Upgrade to versions 10.34.0, 11.4.0 or above.

Impact 6.5 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Learn more about CVSS

Weakness

  • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-522: Insufficiently Protected Credentials

Source file

npm/pnpm/CVE-2026-50017.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Mon, 13 Jul 2026 12:19:51 +0000.