Information Exposure Affecting pnpm package, versions <11.11.0-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.23% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-PNPM-20411690
  • published3 Oct 2026
  • disclosed27 Sept 2026

Introduced: 27 Sep 2026

NewCVE-2026-101043  (opens in a new tab)
CWE-201  (opens in a new tab)

How to fix?

Upgrade Minimos:latest pnpm to version 11.11.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream pnpm package and not the pnpm package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

pnpm versions 11.0.0 before 11.11.0 and 10.7.0 before 10.34.5 expand ${VAR} environment-variable placeholders in the httpProxy, httpsProxy, and noProxy settings read from a project's pnpm-workspace.yaml. Because the manifest is repository-controlled and the proxy keys were omitted from the request-destination key set that otherwise suppresses placeholder expansion for untrusted manifests (as already done for registry, pnprServer, registries and namedRegistries), an attacker who controls a repository's pnpm-workspace.yaml can cause a victim who clones the repository and runs a pnpm command (e.g. pnpm install) to expand environment secrets such as NPM_TOKEN or GITHUB_TOKEN into a proxy hostname or userinfo and route install traffic — and the corresponding DNS lookups — through an attacker-controlled host. The exfiltration occurs during configuration loading, before any lifecycle script executes. Fixed in pnpm 11.11.0 and 10.34.5.

CVSS Base Scores

version 3.1