https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2026-59196.htmlhttps://patchthecve.com/cve/CVE-2026-59196.htmlTue, 07 Jul 2026 19:09:15 +0000HIGH 7.1: pnpm is a package manager. Prior to 10.34.4 and 11.7.0, a crafted lockfile alias could be joined directly under a hoisted node_modules directory. Traversal aliases could escape that directory, while reserved aliases such as .bin or .pnpm could overwrite pnpm-owned layout. This vulnerability is fixehttps://patchthecve.com/cve/CVE-2026-59195.htmlhttps://patchthecve.com/cve/CVE-2026-59195.htmlTue, 07 Jul 2026 19:09:30 +0000HIGH 8.2: 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 whosehttps://patchthecve.com/cve/CVE-2026-59194.htmlhttps://patchthecve.com/cve/CVE-2026-59194.htmlTue, 07 Jul 2026 19:08:57 +0000HIGH 7.1: pnpm is a package manager. Prior to 10.34.4 and 11.7.0, a crafted patch entry could resolve outside the configured patches directory and cause pnpm patch-remove to delete an arbitrary reachable file. This vulnerability is fixed in 10.34.4 and 11.7.0.https://patchthecve.com/cve/CVE-2026-55700.htmlhttps://patchthecve.com/cve/CVE-2026-55700.htmlMon, 29 Jun 2026 21:16:55 +0000HIGH 7.1: pnpm is a package manager. From 11.3.0 until 11.5.3, `pnpm stage download` derived a local filename from registry-controlled package name and version fields. A crafted manifest could escape the selected download directory and overwrite another reachable file. The merged fix validates both fields, dehttps://patchthecve.com/cve/CVE-2026-55699.htmlhttps://patchthecve.com/cve/CVE-2026-55699.htmlMon, 29 Jun 2026 21:16:36 +0000MEDIUM 6.5: pnpm is a package manager. Prior to 10.34.2 and 11.5.3, Manifest bin object keys such as "", ".", and ".." passed pnpm's bin-name guard. When a malicious package was installed globally, later global remove, update, or add-replacement flows could re-derive those names from the installed manifest and https://patchthecve.com/cve/CVE-2026-55698.htmlhttps://patchthecve.com/cve/CVE-2026-55698.htmlTue, 30 Jun 2026 19:03:56 +0000HIGH 8.8: pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can persist package-manager bootstrap metadata in the first YAML document of pnpm-lock.yaml. Before the patch, direct pnpm execution trusted an already resolved packageManagerDependencies entry when the committed env lockfile contained mathttps://patchthecve.com/cve/CVE-2026-55697.htmlhttps://patchthecve.com/cve/CVE-2026-55697.htmlTue, 30 Jun 2026 19:04:04 +0000HIGH 7.5: pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm can install configDependencies declared in pnpm-workspace.yaml before command dispatch. Before the patch, a repository could declare pacquet or @pnpm/pacquet as a config dependency and pnpm treated that repository-controlled dependency as https://patchthecve.com/cve/CVE-2026-55487.htmlhttps://patchthecve.com/cve/CVE-2026-55487.htmlMon, 29 Jun 2026 21:16:26 +0000HIGH 7.5: pnpm is a package manager. Prior to 10.34.2 and 11.5.3, the generic peer-suffix normalizer also stripped parenthesized text from git, URL, tarball, file, and other opaque locators. Approval for one source string could therefore authorize a different attacker-controlled source whose locator normalizehttps://patchthecve.com/cve/CVE-2026-55180.htmlhttps://patchthecve.com/cve/CVE-2026-55180.htmlMon, 29 Jun 2026 21:16:13 +0000MEDIUM 6.5: pnpm is a package manager. Prior to 10.34.2 and 11.5.3, pnpm and pacquet expanded ${ENV_VAR} placeholders from repository-controlled .npmrc and pnpm-workspace.yaml into registry request destinations and registry credentials. A malicious repository could cause dependency resolution to send victim envhttps://patchthecve.com/cve/CVE-2026-50573.htmlhttps://patchthecve.com/cve/CVE-2026-50573.htmlMon, 29 Jun 2026 21:15:58 +0000MEDIUM 6.8: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, `pnpm install` in non-frozen mode can accept new remote package content after detecting that the downloaded tarball does not match the integrity recorded in pnpm-lock.yaml. When a package is already locked with an integrity value, and the regishttps://patchthecve.com/cve/CVE-2026-50021.htmlhttps://patchthecve.com/cve/CVE-2026-50021.htmlMon, 29 Jun 2026 21:15:33 +0000MEDIUM 6.8: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's tarball extraction worker skips integrity verification when the integrity field is absent from the lockfile resolution. If an attacker can both modify pnpm-lock.yaml to remove the integrity: field and cause the referenced registry URL tohttps://patchthecve.com/cve/CVE-2026-50017.htmlhttps://patchthecve.com/cve/CVE-2026-50017.htmlTue, 30 Jun 2026 19:04:10 +0000MEDIUM 6.5: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm can send user-level unscoped npm authentication credentials to a registry chosen by a repository-local .npmrc file. In the reproduced case, the user's npm config contains a default registry and an unscoped _authToken. The repository does nhttps://patchthecve.com/cve/CVE-2026-50016.htmlhttps://patchthecve.com/cve/CVE-2026-50016.htmlMon, 29 Jun 2026 23:57:03 +0000HIGH 8.8: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm allows a transitive dependency alias from registry package metadata to contain path traversal segments. During install, pnpm later uses that alias as a filesystem path when linking dependency nodes. As a result, a registry package can caushttps://patchthecve.com/cve/CVE-2026-50015.htmlhttps://patchthecve.com/cve/CVE-2026-50015.htmlMon, 29 Jun 2026 21:15:11 +0000HIGH 7.3: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm's patch application pipeline (@pnpm/patch-package) performs no path validation on file paths extracted from .patch files. An attacker who contributes a malicious patch file via a pull request can write attacker-controlled content to or delhttps://patchthecve.com/cve/CVE-2026-50014.htmlhttps://patchthecve.com/cve/CVE-2026-50014.htmlMon, 29 Jun 2026 21:14:58 +0000MEDIUM 6.4: pnpm is a package manager. Prior to 10.34.0 and 11.4.0, pnpm passes the lockfile-controlled git resolution.commit value to git fetch without a -- separator or commit-format validation. For git dependencies fetched through the shallow-fetch path, a malicious lockfile can replace the expected 40-charahttps://patchthecve.com/cve/CVE-2026-48995.htmlhttps://patchthecve.com/cve/CVE-2026-48995.htmlMon, 29 Jun 2026 20:30:18 +0000HIGH 7.5: pnpm is a package manager. Prior to 10.33.4 and 11.0.7, a malicious codeload.github.com server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile. The lockfile does not store the hash of the dependencies from https://codeload.github.com. This means that if this s