CVE-2026-101044
Last modified
CVE-2026-101044 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. pacquet, the Rust package-manager component shipped in the pnpm npm package versions >=12.0.0-alpha.0 and <12.0.0-alpha.5, does not validate dependency alias/name paths taken from a lockfile before using them in install-time filesystem joins. When a user installs a project with an attacker-supplied lockfile using --trust-lockfile or a frozen lockfile, alias entries containing path traversal segments (for example '../../escaped-link') are used when creating dependency and package links, bin destinations, hoisted entries, and virtual-store slots, allowing symlinks and directories to be created outside the intended project and node_modules boundary.
Description
pacquet, the Rust package-manager component shipped in the pnpm npm package versions >=12.0.0-alpha.0 and <12.0.0-alpha.5, does not validate dependency alias/name paths taken from a lockfile before using them in install-time filesystem joins. When a user installs a project with an attacker-supplied lockfile using --trust-lockfile or a frozen lockfile, alias entries containing path traversal segments (for example '../../escaped-link') are used when creating dependency and package links, bin destinations, hoisted entries, and virtual-store slots, allowing symlinks and directories to be created outside the intended project and node_modules boundary. Version 12.0.0-alpha.5 validates dependency names and every virtual-store slot path with a shared safe-join containment helper before any filesystem materialization, rejecting traversal, absolute, platform-specific, and reserved names with ERR_PNPM_INVALID_DEPENDENCY_NAME.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| pnpm | pnpm | >= 12.0.0-alpha.0, < 12.0.0-alpha.5 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-101044?
How severe is CVE-2026-101044?
How do I fix CVE-2026-101044?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-101039A vulnerability was identified in FAST FAC1900R 20190827_2.0…10
- CVE-2026-10104The Product Video Gallery for Woocommerce plugin for WordPre…4.4
- CVE-2026-101040A security flaw has been discovered in Ricoh SP 330DN, SP 22…6.5
- CVE-2026-101041The account recovery (password reset) functionality in the v…6.3
- CVE-2026-101042Parse Server is an open-source backend server. In versions >…6.4
- CVE-2026-101043pnpm versions 11.0.0 before 11.11.0 and 10.7.0 before 10.34.…7.4
- CVE-2026-101045Fleet-maintained app install and uninstall scripts for macOS…8
- CVE-2026-101046Fleet before 4.89.0 contains an SQL injection vulnerability …3.1
- CVE-2026-101047Fleet before 4.87.0 does not protect the two endpoints that …5.3
- CVE-2026-101048Cloudreve before 4.17.0 registers the administrative node te…5.4
- CVE-2026-101049Heym before 0.0.53 fails to verify Slack request signatures …6.5
- CVE-2026-10105agno 2.6.5 contains a SQL injection vulnerability in the Cli…8.7
Are you affected by CVE-2026-101044?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
