CVE-2026-50016 is a high-severity path traversal vulnerability in pnpm, the Node.js package manager. In vulnerable versions prior to 10.34.0 and 11.4.0, pnpm permits a transitive dependency alias derived from registry package metadata to contain path traversal segments. During dependency installation and linking, pnpm subsequently uses that alias as a filesystem path when linking dependency nodes. Because the alias is not safely constrained to the intended project directory structure, a malicious package published to a registry can cause pnpm install --ignore-scripts to replace paths inside the current project with symlinks pointing to attacker-controlled dependency package directories. The issue is notable because exploitation does not rely on lifecycle script execution; instead it abuses filesystem path handling during install/link operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
.git/hooks, .husky, .githooks, scripts/, .github/actions/<name>, dist/, or node_modules/.bin. This can enable arbitrary code execution in subsequent developer, build, or CI/CD workflows when those paths are later invoked, as well as integrity compromise of the project workspace and denial of service where expected regular files or directories are replaced. The provided CVSS context indicates high confidentiality, integrity, and availability impact.If you can’t patch tonight, do this now.
pnpm install --ignore-scripts mitigates this issue. As a defensive measure, inspect execution-relevant project paths such as .git/hooks, .husky, .githooks, scripts/, .github/actions/, dist/, and node_modules/.bin for unexpected symlinks after installation, and restrict package installation in developer and CI environments to trusted dependency sources where possible.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.