11.9.0
13 years ago
6 days ago
Known vulnerabilities in the pnpm package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the config and auth-header flow, which binds unscoped user-level npm How to fix Insufficiently Protected Credentials? Upgrade | <10.34.0>=11.0.0 <11.4.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity in the default behavior of How to fix Insufficient Verification of Data Authenticity? Upgrade | <10.34.0>=11.0.0 <11.4.0 |
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 How to fix Relative Path Traversal? Upgrade | <10.34.0>=11.0.0 <11.4.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Missing Support for Integrity Check involving GitHub git dependencies, because the tarball hash for packages resolved from How to fix Missing Support for Integrity Check? Upgrade | <10.33.4>=11.0.0 <11.0.7 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Arbitrary Argument Injection in the git fetcher at How to fix Arbitrary Argument Injection? Upgrade | <10.34.0>=11.0.0 <11.4.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Improper Validation of Integrity Check Value in the tarball extraction process when the How to fix Improper Validation of Integrity Check Value? Upgrade | <10.34.1>=11.0.0 <11.4.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to External Control of File Name or Path through the handling of reserved or malformed How to fix External Control of File Name or Path? Upgrade | <10.34.2>=11.0.0-alpha.0 <11.5.3 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Unsafe Dependency Resolution via the approval process for dependency sources. An attacker can execute unauthorized code during the build lifecycle by crafting a dependency source locator that collides with an approved source after normalization, thereby bypassing intended build policy restrictions. How to fix Unsafe Dependency Resolution? Upgrade | <10.34.2>=11.0.0-alpha.0 <11.5.3 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to External Control of File Name or Path through the How to fix External Control of File Name or Path? Upgrade | <10.34.4>=11.0.0-alpha.0 <11.7.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Directory Traversal via the patch application process. An attacker can overwrite or delete arbitrary files on the filesystem by submitting a malicious How to fix Directory Traversal? Upgrade | <10.34.0>=11.0.0 <11.4.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to External Control of File Name or Path via the lockfile alias handling process. An attacker can overwrite files or directories outside the intended How to fix External Control of File Name or Path? Upgrade | <10.34.4>=11.0.0 <11.7.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Directory Traversal via the How to fix Directory Traversal? Upgrade | <10.34.4>=11.0.0 <11.8.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Use of Weak Hash for path shortening. An attacker can cause collisions in file paths, leading to the overwriting of indirect package dependencies by manipulating package names and versions to generate the same hash value. Note: This is only exploitable if the package names and versions are specifically crafted to exceed 120 characters and share the same hash output. How to fix Use of Weak Hash? Upgrade | <10.0.0-alpha.0 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Untrusted Search Path due to mishandling of overrides and global cache settings even when How to fix Untrusted Search Path? Upgrade | <9.14.4 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Access Control Bypass. It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives. This can result in a package that appears safe on the npm registry or when installed via npm being replaced with a compromised or malicious version when installed via pnpm. How to fix Access Control Bypass? Upgrade | <7.33.4>=8.0.0 <8.6.8 |
pnpm is a Fast, disk space efficient package manager Affected versions of this package are vulnerable to Improper Input Validation via an untrusted search path which causes the application to behave in unexpected ways when users execute PNPM commands in a directory containing malicious content. How to fix Improper Input Validation? Upgrade | <6.15.1 |