CVE-2026-55700: pnpm `stage Download` writes Outside Its Destination Vulnerability

HIGH
Advisory Identifier: GHSA-v23m-ccfg-pq9h
CVSS 7.1
CWE-73 CWE-22
Published
Advisory Summary

CVE-2026-55700 is a HIGH (CVSS 7.1) `stage download` writes outside its destination vulnerability (CWE-73: External Control of File Name or Path) affecting pnpm libraries in the npm ecosystem. The issue involves `stage download` writes outside its destination directory via manifest name/version traversal. Remediation is available by upgrading affected packages to version 11.5.3.

CVE-2026-55700 at a Glance

CVE Identifier CVE-2026-55700
GHSA Identifier GHSA-v23m-ccfg-pq9h
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-73: External Control of File Name or Path
Affected Product pnpm
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-55700

To remediate this vulnerability, upgrade all affected pnpm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pnpm fixed: 11.5.3
npm install pnpm@11.5.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls pnpm

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-55700, inspect your project dependencies using npm:

npm ls pnpm

Analyze the terminal output to locate any version of pnpm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.5.3), your application is affected.

Note: The npm ls pnpm command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-73: External Control of File Name or Path, where the product allows user input to control or influence paths or file names that are used in filesystem operations. In pnpm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The staged-tarball filename traversal reported as GHSA-v23m-ccfg-pq9h / CAND-PNPM-038 is fixed on `main` by [pnpm/pnpm#12303](https://github.com/pnpm/pnpm/pull/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.ts` validates manifest identity and rejects cross-platform path separators. - `releasing/commands/src/stage/download.ts` verifies the resolved destination before writing. - `releasing/commands/src/tarball/summarizeTarball.ts` uses the same filename contract. - `releasing/commands/test/stage.test.ts` covers traversal through both package name and version. - `.changeset/stale-stage-tarballs.md` includes patch bumps for `@pnpm/releasing.commands` and `pnpm`. ## 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 ```text $ git diff --check 65443f4bdf^ 65443f4bdf PASS $ gh pr view 12303 --repo pnpm/pnpm --json state,mergeCommit,statusCheckRollup MERGED as 65443f4bdf ``` ## Validation - 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.ts` cache 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 --check` also 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).

CVE-2026-55700 Affected pnpm Versions

1 component(s)
Fixed Versions:
11.5.3
Product / Package Ecosystem Affected Versions Fixed Version
pnpm
npm
≥ 11.3.0
< 11.5.3
11.5.3

References

Frequently Asked Questions

What is CVE-2026-55700?
CVE-2026-55700 is a security vulnerability in pnpm involving `stage download` writes outside its destination directory via manifest name/version traversal under CWE-73: External Control of File Name or Path.
Which pnpm versions are affected?
Affected versions include releases prior to 11.5.3 across affected packages: pnpm.
What version fixes CVE-2026-55700?
Upgrading to 11.5.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pnpm affected?
Yes, pnpm is affected in releases prior to 11.5.3. Upgrade your dependency to 11.5.3 or later.
What is the CVSS score of CVE-2026-55700?
CVE-2026-55700 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L.
What CWE is associated with CVE-2026-55700?
CVE-2026-55700 is classified under CWE-73: External Control of File Name or Path (The product allows user input to control or influence paths or file names that are used in filesystem operations.).
How can I check npm dependencies for CVE-2026-55700?
Run the dependency tree command: 'npm ls pnpm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v23m-ccfg-pq9h",
  "modified" : "2026-06-26T23:54:52Z",
  "published" : "2026-06-26T23:54:52Z",
  "aliases" : [ "CVE-2026-55700" ],
  "summary" : "pnpm: `stage download` writes outside its destination directory via manifest name/version traversal",
  "details" : "## Summary\n\nThe staged-tarball filename traversal reported as GHSA-v23m-ccfg-pq9h / CAND-PNPM-038 is fixed on `main` by [pnpm/pnpm#12303](https://github.com/pnpm/pnpm/pull/12303), merged as `65443f4bdf1f0db9c8c7dc58fee25252607e9234`.\n\nBefore 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.\n\n## Security boundary\n\n- Package names and semantic versions are validated before they can influence a local filename.\n- POSIX and Windows path separators are rejected by basename checks.\n- Stage download and tarball summary paths use the same filename helper.\n- The resolved output path must remain an immediate child of the selected download directory.\n- The stage identifier is already constrained to a UUID.\n\n## Exploit replay\n\nBefore `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.\n\n## Files changed\n\n- `releasing/commands/src/tarball/safeTarballFilename.ts` validates manifest identity and rejects cross-platform path separators.\n- `releasing/commands/src/stage/download.ts` verifies the resolved destination before writing.\n- `releasing/commands/src/tarball/summarizeTarball.ts` uses the same filename contract.\n- `releasing/commands/test/stage.test.ts` covers traversal through both package name and version.\n- `.changeset/stale-stage-tarballs.md` includes patch bumps for `@pnpm/releasing.commands` and `pnpm`.\n\n## Patch\n\n- Merged PR: https://github.com/pnpm/pnpm/pull/12303\n- Fix commit: `65443f4bdf1f0db9c8c7dc58fee25252607e9234`\n- 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.\n\n## Commands run\n\n```text\n$ git diff --check 65443f4bdf^ 65443f4bdf\nPASS\n$ gh pr view 12303 --repo pnpm/pnpm --json state,mergeCommit,statusCheckRollup\nMERGED as 65443f4bdf\n```\n\n## Validation\n\n- Upstream regression coverage rejects traversal through both manifest name and version and verifies that no outside file is created.\n- Compile and lint, dependency audit, Linux Node.js 22/24/26, CodeQL, and zizmor checks passed on the merged public PR.\n- The Windows Node.js 22 full-suite job timed out in the unrelated `pnpm/test/dlx.ts` cache test after 512 other tests passed. The PR was merged by the maintainer; the failure did not involve the staging code.\n- The earlier private candidate's focused exploit regression, positive control, package compile, ESLint, and `git diff --check` also passed.\n\n## Compatibility\n\nStaging and release commands are TypeScript-only. Pacquet does not expose this command family, so no Rust-side port is required.\n\n## Remaining risk\n\nThe 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.\n\n---\nWritten by an agent (Codex, GPT-5).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "pnpm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "11.3.0"
      }, {
        "fixed" : "11.5.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pnpm/pnpm/security/advisories/GHSA-v23m-ccfg-pq9h"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55700"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pnpm/pnpm/pull/12303"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pnpm/pnpm"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22", "CWE-73" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T23:54:52Z",
    "nvd_published_at" : "2026-06-25T18:16:41Z"
  }
}