Relative Path Traversal Affecting pnpm package, versions <10.34.0>=11.0.0 <11.4.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Relative Path Traversal vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-PNPM-17668134
- published29 Jun 2026
- disclosed26 Jun 2026
- creditHuli
Introduced: 26 Jun 2026
NewCVE-2026-50016 (opens in a new tab)How to fix?
Upgrade pnpm to version 10.34.0, 11.4.0 or higher.
Overview
pnpm is a Fast, disk space efficient package manager
Affected versions of this package are vulnerable to Relative Path Traversal in dependency alias handling, which passes alias names from package metadata into dependency linking as path components and normalizes them with path.join() without validation. An attacker can create symlinks at locations outside node_modules, such as .git/hooks, .husky, or .github/actions, and have their code execute on a later git commit, pnpm test, or pnpm publish, by publishing a dependency whose alias contains traversal segments like @x/../../../../../.git/hooks. Exploitation requires the victim to run pnpm install on a project that pulls in the malicious dependency, directly or transitively, and it proceeds even with pnpm install --ignore-scripts, so that flag is not a mitigation.