How severe is CVE-2026-50017?

CVE-2026-50017 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-50017 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-50017?

CVE-2026-50017 affects Pnpm. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-50017?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-50017 have an EU (EUVD) identifier?

Yes. CVE-2026-50017 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39495.

When was CVE-2026-50017 published?

CVE-2026-50017 was published on 2026-06-25 and last updated on 2026-06-30.

CVE-2026-50017

CVE-2026-50017 is a medium-severity vulnerability in Pnpm with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-200.

Key facts

Severity: Medium (CVSS 3.x base score 6.5)
CVSS v4: 6.9
EPSS exploit prediction: 0% (17th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-39495
Weakness: CWE-200
Affected product: Pnpm
Published: 2026-06-25
Last modified: 2026-06-30

Description

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.

Frequently asked questions

What is CVE-2026-50017?: 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.
How severe is CVE-2026-50017?: CVE-2026-50017 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-50017 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-50017?: CVE-2026-50017 affects Pnpm. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-50017?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-50017 have an EU (EUVD) identifier?: Yes. CVE-2026-50017 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39495.
When was CVE-2026-50017 published?: CVE-2026-50017 was published on 2026-06-25 and last updated on 2026-06-30.

References

https://github.com/pnpm/pnpm/security/advisories/GHSA-cjhr-43r9-cfmw

Affected products (1)

cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:node.js:*:*

More vulnerabilities in Pnpm

CVE-2024-53866 — Critical (CVSS 9.8): The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one…
CVE-2026-55698 — High (CVSS 8.8): pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persist package-manager bootstrap metadata in the…
CVE-2026-50016 — High (CVSS 8.8): pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm allows a transitive dependency alias from registry package…
CVE-2025-69264 — High (CVSS 8.8): pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during…
CVE-2022-26183 — High (CVSS 8.8): PNPM v6.15.1 and below was discovered to contain an untrusted search path which causes the application to behave in…
CVE-2026-59195 — High (CVSS 8.2): pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile…

All CVEs affecting Pnpm →

Other CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities

CVE-2026-27604 — Critical (CVSS 10.0): FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version…
CVE-2026-40965 — Critical (CVSS 10.0): Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a…
CVE-2026-42826 — Critical (CVSS 10.0): Exposure of sensitive information to an unauthorized actor in Azure DevOps allows an unauthorized attacker to disclose…
CVE-2025-29270 — Critical (CVSS 10.0): Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows…
CVE-2025-61481 — Critical (CVSS 10.0): An issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by…
CVE-2025-53624 — Critical (CVSS 10.0): The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user.…

Browse all CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities →