Skip to content
VulniPulse
Sign in
Advisory severityMedium6.5Red Hat Linux

Medium [CVE-2026-50017] Information disclosure of authentication credentials via malicious.npmrc file

This medium-severity Red Hat Linux advisory covers CVE-2026-50017 affecting Red Hat AMQ Broker 7, Red Hat Build of Keycloak, Red Hat JBoss Enterprise Application Platform 8.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-50017 Source published Source updated

VulniPulse record published Record updated

CVE-2026-50017
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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. During normal pnpm operations, the user's authentication token, intended for their default registry, can be inadvertently sent to a different, potentially malicious, registry.

This could lead to the unauthorized disclosure of sensitive authentication tokens. This Moderate impact information disclosure flaw in pnpm allows an attacker to obtain user-level unscoped npm authentication credentials.

When a user runs pnpm commands in a repository with a malicious local `.npmrc` file, their authentication token, intended for their default registry, can be redirected to an attacker-controlled registry. Red Hat severity: Moderate — CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-201.

Is CVE-2026-50017 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50017 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-50017?

Upgrade to a fixed release named by Red Hat:

  • 10.34.0
  • 11.4.0

Confirm against the vendor advisory before you patch.

Affected versions
  • < 10.34.0
  • < 11.4.0

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • 10.34.0
  • 11.4.0

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, ensure that all npm authentication tokens are explicitly URL-scoped rather than relying on unscoped, user-level configurations. Additionally, avoid executing pnpm commands in untrusted repositories, as a malicious `.npmrc` file can redirect authentication credentials to an attacker.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.