CVE-2026-55180 pnpm: Repository config can expand victim environment secrets into registry requests before scripts run

Medium 6.5 Published Updated

A malicious repository can leak victim environment secrets to an attacker-controlled registry during dependency resolution in pnpm.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-55180?

CVE-2026-55180 is a medium-severity vulnerability in pnpm, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm and pacquet expanded ${ENV_VAR} placeholders from repository-controlled .npmrc and pnpm-workspace.yaml into registry request destinations and registry credentials. A malicious repository could cause dependency resolution to send victim environment secrets to an attacker-selected registry before lifecycle scripts run. This vulnerability is fixed in 10.34.2 and 11.5.3.

Weakness: CWE-522, CWE-201, CWE-200

Which versions are affected by CVE-2026-55180?

4 open source packages ship an affected version, including pnpm. It affects 1 product.

PackageAffectedFixed in
pnpm npmAll versions10.34.2
pnpm npmAll versions10.34.2
pnpm npmFrom 11.0.011.5.3
pnpm npmFrom 11.0.011.5.3

Products include Pnpm Pnpm.

How do I fix CVE-2026-55180?

Upgrade pnpm to a fixed version for your release line: 10.34.2 or 11.5.3.

Is CVE-2026-55180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55180 exists.

Sources

Also known as GHSA-3qhv-2rgh-x77r, MINI-hcf4-cm48-ccpg, ROOT-APP-NPM-CVE-2026-55180.

Is CVE-2026-55180 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free