dbcve.org
PnpmApplication

CVE-2025-69264

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 10.26.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

pnpm v10.0.0-10.25 contains a vulnerability where git-hosted dependencies can execute arbitrary code during pnpm install by running prepare, prepublish, and prepack scripts during the fetch phase. This bypasses pnpm v10's security feature that blocks postinstall scripts via onlyBuiltDependencies, enabling unauthenticated remote code execution without user consent.

MitigationUpgrade pnpm to version 10.26.0 or later to remediate this vulnerability. Review and audit any git-hosted dependencies in your project to ensure no malicious code was executed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PnpmApplication
Affected:>= 10.0.0, < 10.26.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check pnpm version
    Run 'pnpm --version' in the terminal
    Affected if The version is 10.0.0 or higher but lower than 10.26.0
  2. Identify git-hosted dependencies
    Inspect package.json for dependencies that use git URLs (e.g., git+https://, git://, or hosted-git-specific formats) or check pnpm-lock.yaml for entries with 'resolved' pointing to git repositories
    Affected if The project has one or more dependencies resolved from git repositories
  3. Inspect git dependency package.json for lifecycle scripts
    For each git-hosted dependency, clone or fetch the repository and examine its package.json for 'scripts' containing 'prepare', 'prepublish', or 'prepack' entries
    Affected if Any git-hosted dependency defines prepare, prepublish, or prepack scripts in its package.json
  4. Verify script execution configuration
    Check pnpm configuration files (pnpm-workspace.yaml, .npmrc with public-hoist-pattern, package.json settings) for whether lifecycle script execution is explicitly enabled for dependencies
    Affected if Configuration allows lifecycle scripts to run during install for dependencies (note: pnpm v10 disables these by default, so this check identifies if the default protection is overridden)

You are affected if pnpm version is between 10.0.0 and 10.25.x AND your project uses git-hosted dependencies that contain prepare, prepublish, or prepack scripts in their package.json.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.26.0 or later
Fixed in 10.26.0
Vendor patch github.com →
Interim mitigation

Upgrade pnpm to version 10.26.0 or later to remediate this vulnerability. Review and audit any git-hosted dependencies in your project to ensure no malicious code was executed.

Recommended fix High confidence

pnpm 10.26.0 or later

  1. Check your current pnpm version by running: pnpm --version
  2. Upgrade pnpm to version 10.26.0 or later using: npm install -g [email protected]
  3. Verify the upgrade was successful by running: pnpm --version
  4. Ensure your pnpm version is >= 10.26.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pnpm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69264 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data