pnpm: Hoisted install imports lockfile alias outside node_modules

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-59196: 0.40% estimated exploitation activity in the next 30 days; percentile 34.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The hoisted dependency alias issue tracked as GHSA-fr4h-3cph-29xv / CAND-PNPM-059 has been addressed in both pnpm and pacquet. A crafted lockfile alias could be joined directly under a hoisted nodemodules directory. Traversal aliases could escape that directory, while reserved aliases such as .bin or .pnpm could overwrite pnpm-owned layout. This patch validates package-name semantics and path containment before graph insertion or filesystem work. Security boundary - The TypeScript hoisted graph uses the shared safe join helper at the actual dep.name sink. - The helper rejects traversal, absolute, platform-specific, and reserved package names. - Pacquet validates the hoister's dep.0.name before adding the graph node or recursing. - Both implementations return ERRPNPMINVALIDDEPENDENCYNAME. - Pacquet uses the same dependency-name containment rule at its hoisted graph sink as it uses for direct dependency aliases. Exploit replay Before the patch, a traversal alias in a hoisted…

Published by the source

27 Jun 2026, 00:02 UTC

Last modified by the source

8 Jul 2026, 08:27 UTC

Source last checked

26 Oct 2026, 12:56 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fr4h-3cph-29xv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fr4h-3cph-29xv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59196

Advisory: pnpm: Hoisted install imports lockfile alias outside node_modules
IDs: CVE-2026-59196, GHSA-fr4h-3cph-29xv
Record: https://patchnext.com/advisories/cve-2026-59196 (revision 2, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pnpm 11.7.0, 10.34.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm pnpm: affected < 10.34.4; >= 11.0.0, < 11.7.0; fixed in 10.34.4, 11.7.0

## Suggested inspection (read-only)
- `npm ls pnpm --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pnpm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fr4h-3cph-29xv (OSV record GHSA-fr4h-3cph-29xv lists affected ranges: npm pnpm >=0 =11.0.0 <11.7.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fr4h-3cph-29xv (GitHub-reviewed advisory GHSA-fr4h-3cph-29xv lists affected ranges: npm pnpm >=0 =11.0.0 <11.7.0)

Commands are suggestions: review each one before running it.