CVE-2026-59195: pnpm is a package manager

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

pnpm: upgrade to 10.34.4, 11.8.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-59195 being exploited?

CVE-2026-59195 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-59195 affect?

CVE-2026-59195 affects pnpm. Severity is high (CVSS 8.2). pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A ma

Q: How urgent is CVE-2026-59195?

Priority 42/100. High severity; Public exploit reference

This month

HIGH 8.2UPGRADE

CVE-2026-59195 is a high-severity flaw (CVSS 8.2) 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. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a syml

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

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

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

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

Am I affected?

Timeline

2026-07-06 16:16 UTCPublished CVE record published
2026-07-07 19:09 UTCUpdated Record last modified

pnpm pnpm UPGRADE

Affected: < 10.34.4 · >= 11.0.0 and < 11.8.0

Fixed in: 10.34.4, 11.8.0

Safe to downgrade to: a release before 11.0.0

1. Check installed version

npm ls pnpm

2. UPGRADE to 10.34.4

npm install pnpm@">=10.34.4"

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

npm view pnpm versions npm install pnpm@"<11.0.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-59195?

pnpm: upgrade to 10.34.4, 11.8.0. Exact commands for each OS are on this page.

Is CVE-2026-59195 being exploited?

CVE-2026-59195 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-59195 affect?

CVE-2026-59195 affects pnpm. Severity is high (CVSS 8.2). pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A ma

How urgent is CVE-2026-59195?

Priority 42/100. High severity; Public exploit reference

Related CVEs

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
CVE-2026-55698 HIGH 8.8 UPGRADE pnpm is a package manager

References

← Back to latest CVEs