Quick answers
- Is CVE-2026-55700 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55700 being exploited in the wild.
- How severe is CVE-2026-55700?
- High severity, with a CVSS score of 7.1, published 25 June 2026.
- Which products and versions are affected?
- pnpm (npm) >= 11.3.0, < 11.5.3, SEMVER:introduced=11.3.0,fixed=11.5.3.
- Is there a fix for CVE-2026-55700?
- Yes. pnpm (npm): upgrade to 11.5.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55700 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-55700?
- Check whether you run pnpm (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pnpm (npm): upgrade to 11.5.3 or later
npm install pnpm@11.5.3
Technical details
A path traversal vulnerability (CWE-22/CWE-73) exists in pnpm's `stage download` command. The root cause is the improper neutralization of package name and version fields from registry-controlled manifests when deriving local filenames. An attacker can craft a manifest with traversal sequences (e.g., ../) in these fields to escape the designated download directory and overwrite arbitrary reachable files. Exploitation requires a user to run the affected command against a malicious manifest. The vulnerability is fixed in version 11.5.3 by implementing strict validation of package names and versions and verifying that the final resolved path remains within the target directory.
Affected products
- pnpm pnpm >= 11.3.0, < 11.5.3
Identifiers
- CVE-2026-55700
- GHSA-v23m-ccfg-pq9h
Timeline
- 2026-06-15: disclosed: Initial disclosure by zkochan
- 2026-06-25: advisory: NVD publication
- 2026-06-26: patched: GitHub Advisory reviewed and updated