CVE-2026-55700: pnpm: `stage download` writes outside its destination directory via manifest name/version traversal
Summary The staged-tarball filename traversal reported as GHSA-v23m-ccfg-pq9h / CAND-PNPM-038 is fixed on main by pnpm/pnpm#12303, merged as 65443f4bdf1f0db9c8c7dc58fee25252607e9234. Before the fix, pnpm stage download derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file.
Published Jun 26, 2026
Affected packages
pnpm
- Ecosystem
- npm
- Affected
- >= 11.3.0, < 11.5.3
- Fixed in
- 11.5.3
- Check
npm ls pnpm
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The staged-tarball filename traversal reported as GHSA-v23m-ccfg-pq9h / CAND-PNPM-038 is fixed on main by pnpm/pnpm#12303, merged as 65443f4bdf1f0db9c8c7dc58fee25252607e9234.
Before the fix, pnpm stage download derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields, derives one safe filename, and verifies the final destination before writing.
Security boundary
- Package names and semantic versions are validated before they can influence a local filename.
- POSIX and Windows path separators are rejected by basename checks.
- Stage download and tarball summary paths use the same filename helper.
- The resolved output path must remain an immediate child of the selected download directory.
- The stage identifier is already constrained to a UUID.
Exploit replay
Before 65443f4bdf, a traversal-bearing manifest version could make the command write outside the selected directory. After the fix, malicious package names fail with ERR_PNPM_INVALID_PACKAGE_NAME, malicious versions fail with ERR_PNPM_INVALID_PACKAGE_VERSION, no outside file is created, and the download directory remains empty.
Files changed
releasing/commands/src/tarball/safeTarballFilename.tsvalidates manifest identity and rejects cross-platform path separators.releasing/commands/src/stage/download.tsverifies the resolved destination before writing.releasing/commands/src/tarball/summarizeTarball.tsuses the same filename contract.releasing/commands/test/stage.test.tscovers traversal through both package name and version..changeset/stale-stage-tarballs.mdincludes patch bumps for@pnpm/releasing.commandsandpnpm.
Patch
- Merged PR: https://github.com/pnpm/pnpm/pull/12303
- Fix commit:
65443f4bdf1f0db9c8c7dc58fee25252607e9234 - The private candidate branch was not submitted because it conflicts with and is superseded by the merged fix. The upstream patch is slightly stronger because it covers malicious package names as well as versions.
Commands run
$ git diff --check 65443f4bdf^ 65443f4bdf
PASS
$ gh pr view 12303 --repo pnpm/pnpm --json state,mergeCommit,statusCheckRollup
MERGED as 65443f4bdfValidation
- Upstream regression coverage rejects traversal through both manifest name and version and verifies that no outside file is created.
- Compile and lint, dependency audit, Linux Node.js 22/24/26, CodeQL, and zizmor checks passed on the merged public PR.
- The Windows Node.js 22 full-suite job timed out in the unrelated
pnpm/test/dlx.tscache test after 512 other tests passed. The PR was merged by the maintainer; the failure did not involve the staging code. - The earlier private candidate's focused exploit regression, positive control, package compile, ESLint, and
git diff --checkalso passed.
Compatibility
Staging and release commands are TypeScript-only. Pacquet does not expose this command family, so no Rust-side port is required.
Remaining risk
The final fs.writeFile follows a pre-existing symlink at the exact in-directory output name. That requires separate local filesystem access and is not controllable through the registry manifest traversal described here.
--- Written by an agent (Codex, GPT-5).
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-82392
pnpm: Virtual store linker path traversal via unvalidated depPath name in lockfileToDepGraph
high7.1Sep 2, 2026CVE-2026-82393
pnpm: A tarball dependency's manifest `name` escapes node_modules → arbitrary file write/overwrite on install
high7.5Sep 2, 2026GHSA-2rx9-3g3h-c2jv
pnpm: pacquet trust-lockfile install can create dependency symlinks outside the project
high7.1Sep 1, 2026GHSA-vx52-2968-3vc6
pnpm: Environment secrets exfiltrated via env-placeholder expansion in proxy settings read from an untrusted pnpm-workspace.yaml
high7.4Sep 1, 2026GHSA-72r4-9c5j-mj57
pnpm: `patch-remove` could delete project-selected files outside the patches directory
high7.1Jun 27, 2026GHSA-fr4h-3cph-29xv
pnpm: Hoisted install imports lockfile alias outside node_modules
high7.1Jun 27, 2026
