CVE-2026-55700: pnpm is a package manager

Q: How do I fix CVE-2026-55700?

pnpm: upgrade to 11.5.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-55700 being exploited?

CVE-2026-55700 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-55700 affect?

CVE-2026-55700 affects pnpm. Severity is high (CVSS 7.1). 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 anot

Q: How urgent is CVE-2026-55700?

Priority 39/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-55700 is a high-severity flaw (CVSS 7.1) affecting pnpm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-22, CWE-73
Published	2026-06-25
Last modified	2026-06-29

Publisher (CNA): GitHub, Inc. · Vendor: pnpm

Last updated 2026-06-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-25 18:16 UTCPublished CVE record published
2026-06-29 21:16 UTCUpdated Record last modified

pnpm pnpm UPGRADE

Affected: >= 11.3.0 and < 11.5.3

Fixed in: 11.5.3

Safe to downgrade to: a release before 11.3.0

1. Check installed version

npm ls pnpm

2. UPGRADE to 11.5.3

npm install pnpm@">=11.5.3"

3. If no update is available yet, DOWNGRADE to a release before 11.3.0

npm view pnpm versions npm install pnpm@"<11.3.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-55700?

pnpm: upgrade to 11.5.3. Exact commands for each OS are on this page.

Is CVE-2026-55700 being exploited?

CVE-2026-55700 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-55700 affect?

CVE-2026-55700 affects pnpm. Severity is high (CVSS 7.1). 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 anot

How urgent is CVE-2026-55700?

Priority 39/100. High severity; Public exploit reference

Related CVEs

CVE-2026-59195 HIGH 8.2 UPGRADE pnpm is a package manager
CVE-2026-59196 HIGH 7.1 UPGRADE pnpm is a package manager
CVE-2026-59194 HIGH 7.1 UPGRADE pnpm is a package manager
CVE-2026-50017 MEDIUM 6.5 UPGRADE pnpm is a package manager
CVE-2026-55697 HIGH 7.5 UPGRADE pnpm is a package manager

References

← Back to latest CVEs