CVE-2026-50015: pnpm Path Traversal in Patch Application

Technical summary

The @pnpm/patch-package module fails to validate file paths extracted from .patch files before applying them to the filesystem. The vulnerability stems from insufficient sanitization of diff --git header paths, which commonly contain relative path sequences that can escape the package directory boundary. An attacker crafting a patch with paths such as ../../sensitive/file enables arbitrary file write or deletion with the privileges of the user executing pnpm install. The attack vector is low-complexity and leverages pull request mechanisms—a common development workflow—making it accessible to internal or external contributors. The CVSS 3.1 score of 7.3 (HIGH) reflects high integrity and availability impact without confidentiality risk.

Business impact

Development teams using pnpm face supply-chain risk during routine dependency updates and patch application workflows. A successful attack could result in system file corruption, configuration tampering, or deletion of critical application files without detection during code review, since patch files are often opaque to human reviewers. For organizations with automated CI/CD pipelines that run pnpm install without manual review, the blast radius extends to build infrastructure and downstream deployments. Trust in internally maintained patches and community contributions is compromised until upgrades are applied.

Affected systems

pnpm versions prior to 10.34.0 and 11.4.0 are affected. Any system or CI/CD pipeline running a vulnerable version and processing .patch files—whether from pull requests, internal repositories, or package updates—is at risk. The impact depends on the privileges of the user running pnpm install; developers and automated build systems are primary targets.

Exploitability

Exploitability is straightforward for an attacker with pull request access or the ability to contribute patches to a project using pnpm. The attack requires user interaction (a developer running pnpm install) and relies on the difficulty of detecting traversal sequences in patch file headers during code review. No special tools or privileges are needed to craft the malicious patch, and the payload executes immediately during install, making detection challenging if filesystem changes are not monitored.

Remediation

Upgrade pnpm to version 10.34.0 or later (or 11.4.0 or later for the 11.x branch). Organizations should prioritize updates in development environments and CI/CD pipelines. Additionally, implement code review practices that include scrutiny of .patch file paths, use of signed commits to verify contributor identity, and monitoring of filesystem changes during package installation.

Patch guidance

Apply updates from pnpm's official release channels: pnpm 10.34.0 or later addresses the vulnerability in the 10.x series, and pnpm 11.4.0 or later is the fix for 11.x users. Verify the patched version against the vendor advisory to confirm the specific build resolves this issue. For organizations with locked dependency versions, update pnpm in your package.json or lock files and re-test development and build workflows before rolling out to CI/CD pipelines.

Detection guidance

Monitor pnpm installation logs and filesystem activity for unexpected file writes or deletions outside project directories. Audit .patch files in repositories for paths containing ../../ sequences or other relative traversal patterns. Implement pre-commit hooks to validate patch file structure and alert on suspicious paths. Check current pnpm version across development machines and CI/CD runners using pnpm -v or package lock metadata to identify systems still running vulnerable versions.

Why prioritize this

This vulnerability merits immediate attention due to its combination of high integrity and availability impact, ease of exploitation, and prevalence of pnpm in modern JavaScript development workflows. The supply-chain attack vector via pull requests means the risk is not limited to external threats; insider risk or compromised accounts can weaponize the vulnerability. The opaque nature of patch files in code review makes detection difficult, increasing the likelihood of successful exploitation before discovery.

Risk score, explained

The CVSS 3.1 score of 7.3 (HIGH) reflects the vulnerability's high impact on file system integrity and availability (arbitrary write/delete), low attack complexity, and requirement for low privilege (user contribution via pull request) combined with user interaction (running pnpm install). The absence of confidentiality impact prevents a critical rating, but the attack's ease and supply-chain implications justify aggressive remediation prioritization beyond the numerical score alone.

Frequently asked questions