CVE-2026-59195 pnpm vulnerability
pnpm is a package manager. Prior to 10.34.4 and 11.8.0, pnpm accepts package names from the env lockfile configDependencies section and uses those names directly when creating config dependency symlinks under node_modules/.pnpm-config. A malicious repository can commit a crafted pnpm-lock.yaml whose env-lockfile document contains a traversal-shaped config dependency name. During pnpm install, pnpm installs the config dependency and creates a symlink at a path derived from that name. This vulnerability is fixed in 10.34.4 and 11.8.0.
Quick answer
pnpm should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
pnpm is affected by CVE-2026-59195, a path traversal and arbitrary file operation risk. pnpm is a package manager. The recommended remediation is to update to pnpm 10.34.4, pnpm 11.8.0, or a later fixed release for the deployed major branch. Until the update is complete, avoid env lockfile configDependencies from untrusted repositories and review node_modules/.pnpm-config symlinks, review logs, and reduce exposure of the affected package, route, provider, or service workflow.
- Inventory every deployment, package, dependency, build runner, integration, route, service, and managed environment that uses pnpm.
- Confirm the installed version/build and compare it with versions prior to 10 and the source advisory for CVE-2026-59195.
- Apply the vendor-supported fix: update to pnpm 10.34.4, pnpm 11.8.0, or a later fixed release for the deployed major branch.
- If the update cannot be applied immediately, avoid env lockfile configDependencies from untrusted repositories and review node_modules/.pnpm-config symlinks; disable unnecessary public access, package-install paths, file processing, webhooks, message consumers, or high-risk integrations until patched.
- Review application, CI/CD, package manager, container, reverse-proxy, WAF, authentication, route, and audit logs for activity related to CVE-2026-59195.
- Rotate sessions, API tokens, package registry credentials, cloud credentials, webhook secrets, service credentials, and administrator passwords if logs or affected data indicate compromise, credential exposure, or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or build agents when appropriate, and remove temporary files, malicious artifacts, stored payloads, or unsafe configuration created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm pnpm now reports pnpm 10.34.4, pnpm 11.8.0, or a later fixed release for the deployed major branch or a later vendor-supported fixed release/build for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-59195, using a safe regression test, dependency inventory, or vendor validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, path traversal, header manipulation, credential exposure, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, dependency check, route regression test, or integration test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup, rebuild, or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59195?
pnpm should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.