Approved changes feed: RSS · Atom

cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:*:node.js:*

part: a version: * update: *

VendorPnpm (9348721a-c616-5878-ac62-b83f60779a08)
ProductPnpm (75993f86-f313-5397-b0b1-ebc05afc5d9b)
Edition*
Language*
Software edition*
Target software*
Target hardwarenode.js
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-69264 vulnerable 2026-06-08 07:41:22.308668 pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"
HIGH (8.8)
pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature "Dependency lifecycle scripts execution disabled by default". While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0.
Published: 2026-01-07T21:53:09.806Z
Updated: 2026-09-14T12:04:32.632Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-69263 vulnerable 2026-06-08 07:41:22.308295 pnpm Lockfile Integrity Bypass Allows Remote Dynamic Dependencies
HIGH (7.5)
pnpm is a package manager. Versions 10.26.2 and below store HTTP tarball dependencies (and git-hosted tarballs) in the lockfile without integrity hashes. This allows the remote server to serve different content on each install, even when a lockfile is committed. An attacker who publishes a package with an HTTP tarball dependency can serve different code to different users or CI/CD environments. The attack requires the victim to install a package that has an HTTP/git tarball in its dependency tree. The victim's lockfile provides no protection. This issue is fixed in version 10.26.0.
Published: 2026-01-07T21:31:07.567Z
Updated: 2026-09-14T12:04:25.725Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-69262 vulnerable 2026-06-08 07:41:22.307933 pnpm vulnerable to Command Injection via environment variable substitution
HIGH (7.6)
pnpm is a package manager. Versions 6.25.0 through 10.26.2 have a Command Injection vulnerability when using environment variable substitution in .npmrc configuration files with tokenHelper settings. An attacker who can control environment variables during pnpm operations could achieve Remote Code Execution (RCE) in build environments. This issue is fixed in version 10.27.0.
Published: 2026-01-07T22:30:07.428Z
Updated: 2026-02-26T15:04:55.349Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-53866 vulnerable 2026-06-08 06:54:15.653352 pnpm vulnerable to no-script global cache poisoning via overrides / `ignore-scripts` evasion
The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace.
Published: 2024-12-10T17:12:44.629Z
Updated: 2025-12-31T01:11:35.531Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-47829 vulnerable 2026-06-08 06:48:13.328148 pnpm uses the md5 path shortening function causes packet paths to coincide, which causes indirect packet overwriting
MEDIUM (6.5)
pnpm is a package manager. Prior to version 10.0.0, the path shortening function uses the md5 function as a path shortening compression function, and if a collision occurs, it will result in the same storage path for two different libraries. Although the real names are under the package name /node_modoules/, there are no version numbers for the libraries they refer to. This issue has been patched in version 10.0.0.
Published: 2025-04-23T15:42:12.623Z
Updated: 2025-04-23T16:08:45.843Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.