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.
Security readout for executives and security teams
Plain-English summary
pnpm v10’s promised default blocking of dependency lifecycle scripts could be bypassed by git-hosted dependencies. A malicious or compromised git dependency could run code during install, affecting developer machines or CI runners that install packages. The issue is fixed in pnpm 10.26.0.
Executive priority
Treat as a high-priority build-chain issue. Prioritize pnpm upgrades in CI and developer environments because compromise could expose source code, tokens, or build artifacts during routine dependency installation.
Technical view
In pnpm 10.0.0 through versions before 10.26.0, git dependencies can execute prepare, prepublish, and prepack scripts during fetch despite the onlyBuiltDependencies lifecycle-script control. The advisory describes arbitrary code execution during pnpm install, with CVSS 3.1 score 8.8 and CWE-693.
Likely exposure
Exposure is most likely in JavaScript projects using pnpm v10 before 10.26.0, especially where package manifests or lockfiles include git-hosted dependencies. CI/CD workers, build agents, and developer workstations are the main assets at risk during dependency installation.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a user or automated process to run pnpm install against a project containing a malicious or compromised git-hosted dependency.
Researcher notes
Focus validation on pnpm v10 behavior with git-hosted dependencies and lifecycle scripts executed during fetch. Evidence supports the bypass and fixed version, but the provided sources do not establish real-world exploitation or affected downstream products.
Mitigation direction
Upgrade pnpm to version 10.26.0 or later.
Review projects for git-hosted dependencies before running installs.
Avoid untrusted git-hosted dependencies until vendor guidance is applied.
Check pnpm advisory updates for any additional hardening guidance.
Validation and detection
Confirm installed pnpm versions are not 10.0.0 through before 10.26.0.
Inspect package manifests and lockfiles for git-hosted dependencies.
Review CI images and developer tooling for pinned pnpm versions.
Check build logs for dependency lifecycle script execution during pnpm installs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-693 · source CWE mapping
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.