CVE-2026-50017: pnpm is a package manager

Q: How do I fix CVE-2026-50017?

pnpm: upgrade to 10.34.0, 11.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-50017 being exploited?

CVE-2026-50017 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-50017 affect?

CVE-2026-50017 affects pnpm. Severity is medium (CVSS 6.5). 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 defaul

Q: How urgent is CVE-2026-50017?

Priority 37/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2026-50017 is a medium-severity flaw (CVSS 6.5) affecting pnpm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 th

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-200, CWE-522
Published	2026-06-25
Last modified	2026-06-30

Publisher (CNA): GitHub, Inc. · Vendor: pnpm

Last updated 2026-06-30 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-25 18:16 UTCPublished CVE record published
2026-06-30 19:04 UTCUpdated Record last modified

pnpm pnpm UPGRADE

Affected: < 10.34.0 · >= 11.0.0 and < 11.4.0

Fixed in: 10.34.0, 11.4.0

Safe to downgrade to: a release before 11.0.0

1. Check installed version

npm ls pnpm

2. UPGRADE to 10.34.0

npm install pnpm@">=10.34.0"

3. If no update is available yet, DOWNGRADE to a release before 11.0.0

npm view pnpm versions npm install pnpm@"<11.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-50017?

pnpm: upgrade to 10.34.0, 11.4.0. Exact commands for each OS are on this page.

Is CVE-2026-50017 being exploited?

CVE-2026-50017 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-50017 affect?

CVE-2026-50017 affects pnpm. Severity is medium (CVSS 6.5). 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 defaul

How urgent is CVE-2026-50017?

Priority 37/100. Public exploit reference

Related CVEs

CVE-2026-59195 HIGH 8.2 UPGRADE pnpm is a package manager
CVE-2026-59196 HIGH 7.1 UPGRADE pnpm is a package manager
CVE-2026-59194 HIGH 7.1 UPGRADE pnpm is a package manager
CVE-2026-55697 HIGH 7.5 UPGRADE pnpm is a package manager
CVE-2026-55698 HIGH 8.8 UPGRADE pnpm is a package manager

References

← Back to latest CVEs