Is CVE-2026-101044 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101044 being exploited in the wild.

How severe is CVE-2026-101044?

High severity, with a CVSS score of 7.1, published 27 September 2026.

Which products and versions are affected?

Pnpm >=12.0.0-alpha.0, <12.0.0-alpha.5.

Is there a fix for CVE-2026-101044?

A patch was published on 2026-09-27: Fixed in version 12.0.0-alpha.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101044 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-101044?

Check whether you run Pnpm 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.

CVE-2026-101044: pnpm path traversal in lockfile alias validation

Q: Is there a fix for CVE-2026-101044?

A patch was published on 2026-09-27: Fixed in version 12.0.0-alpha.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-101044 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-101044?

Check whether you run Pnpm 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.

CVE-2026-101044 · Severity: high · CVSS 7.1 · Published 2026-09-27

pnpm is a package manager for JavaScript that installs project dependencies. Versions 12.0.0-alpha.0 through 12.0.0-alpha.4 fail to validate dependency alias paths from lockfiles, allowing attackers to create symlinks and directories outside the intended project directory when a user installs with a malicious lockfile. This could expose the system to arbitrary file manipulation and potential code execution through specially crafted links.

Technologies: Pnpm. Vendors: Pnpm.

Quick answers

Is CVE-2026-101044 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101044 being exploited in the wild.
How severe is CVE-2026-101044?: High severity, with a CVSS score of 7.1, published 27 September 2026.
Which products and versions are affected?: Pnpm >=12.0.0-alpha.0, <12.0.0-alpha.5.
Is there a fix for CVE-2026-101044?: A patch was published on 2026-09-27: Fixed in version 12.0.0-alpha.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101044 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101044?: Check whether you run Pnpm 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.

Technical details

The pacquet Rust component in pnpm does not sanitize dependency alias paths from lockfiles before using them in filesystem operations, allowing path traversal sequences like '../../' to escape the node_modules boundary. An attacker-controlled lockfile combined with --trust-lockfile or frozen lockfile mode permits creation of symlinks and directories outside the intended containment. The fix validates all dependency names and virtual-store paths using a safe-join helper before any filesystem materialization, rejecting traversal and absolute paths with ERR_PNPM_INVALID_DEPENDENCY_NAME.

Affected products

pnpm pnpm >=12.0.0-alpha.0, <12.0.0-alpha.5

Timeline

2026-09-27: disclosed
2026-09-27: patched: Fixed in version 12.0.0-alpha.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.