Skip to content
Noroxi
CVE-2026-55700· NVD / CVE Program· CNA GitHub_M

pnpm: stage download writes outside destination via manifest version traversal

pnpm is a package manager. From 11.3.0 until 11.5.3, `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. This vulnerability is fixed in 11.5.3.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Jun 29, 2026
EPSS
0.4% · 34th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
pnpmpnpm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • pnpm pnpm11.3.0 and later · before 11.5.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • pnpm pnpm

    • >= 11.3.0, < 11.5.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmpnpmfrom 11.3.0 · before 11.5.311.5.3

Same product

pnpm: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-69264pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"
    39Monitor
  • CVE-2023-37478pnpm incorrectly parses tar archives relative to specification
    39Monitor
  • CVE-2026-55698pnpm: Project env lockfile can short-circuit package-manager resolution and execute lockfile-selected pnpm bytes
    35Monitor
  • CVE-2026-55697pnpm: Repository-controlled configDependencies can select a pacquet native install engine
    35Monitor
  • CVE-2026-55487pnpm: manifest identity spoof satisfies allowBuilds and runs attacker lifecycle
    35Monitor
  • CVE-2026-50016pnpm: Transitive dependency alias path traversal allows project path override via symlink replacement
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
pnpm pnpm11.5.3 · descriptionVendor (CNA)
npm:pnpm11.5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5919511 days apartpnpm: Path traversal in configDependencies env lockfile allows symlink creation outside node_modules/.pnpm-config
    32Monitor
  • CVE-2026-8239367 days apartpnpm: A tarball dependency's manifest `name` escapes node_modules → arbitrary file write/overwrite on install
    30Monitor
  • CVE-2026-500150 days apartpnpm: Arbitrary File Write/Delete via Malicious Patch File (Path Traversal)
    29Monitor
  • CVE-2026-5919411 days apartpnpm: patch-remove could delete project-selected files outside the patches directory
    28Monitor
  • CVE-2026-5919611 days apartpnpm: hoisted install imports lockfile alias outside node_modules
    28Monitor
  • CVE-2026-8239267 days apartpnpm: Virtual store linker path traversal via unvalidated depPath name in lockfileToDepGraph
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records