What is the CVSS score of CVE-2025-69264?

CVE-2025-69264 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of pnpm are affected by CVE-2025-69264?

A critical code execution flaw in pnpm package manager (versions 10.0.0-10.25) allows remote attackers to execute arbitrary code on developer machines and CI/CD infrastructure during routine…. A patch is available.

Is there a public PoC exploit available for CVE-2025-69264?

Yes, a public proof-of-concept exploit is available for CVE-2025-69264. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-69264?

Within 24 hours: Inventory all systems running pnpm 10.0.0-10.25, including developer workstations and CI/CD agents; assess which teams or projects are affected. Within 7 days: Upgrade all pnpm installations to version 10.26.0 or later; review recent builds from potentially affected environments for unexpected modifications. Within 30 days: Conduct code review of recent production releases and consider re-running security audits on build artifacts generated during the vulnerable window.

pnpm CVE-2025-69264

CRITICAL

Protection Mechanism Failure (CWE-693)

2026-01-07 security-advisories@github.com

GHSA-379q-355j-w6rj

RCE Pnpm

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

vuln.today AI

8.8 HIGH

Network-delivered malicious git dependency yields full host RCE (C/I/A High), but a victim must initiate install of an attacker-controlled dependency, so UI:R rather than UI:N.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

8.8 HIGH

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

Red Hat

8.8 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Jun 30, 2026 - 04:11 vuln.today

v5 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 04:10 vuln.today

v4 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 04:10 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 30, 2026 - 04:09 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 30, 2026 - 03:23 vuln.today

cvss_changed

Severity Changed

Jun 30, 2026 - 03:23 NVD

HIGH CRITICAL

CVSS changed

Jun 30, 2026 - 03:23 NVD

8.8 (HIGH) 9.8 (CRITICAL)

Analysis Generated

Mar 12, 2026 - 21:54 vuln.today

PoC Detected

Jan 12, 2026 - 21:53 vuln.today

Public exploit code

Patch released

Jan 12, 2026 - 21:53 nvd

Patch available

CVE Published

Jan 07, 2026 - 22:15 nvd

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on pnpm (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 10.0.0.

DescriptionNVD

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.

AnalysisAI

Arbitrary code execution in the pnpm package manager (versions 10.0.0 through 10.25) lets a git-hosted dependency run code on a developer or CI machine during pnpm install, bypassing the v10 default protection that disables dependency lifecycle scripts. Although v10 blocks postinstall via the onlyBuiltDependencies allowlist, git dependencies still run prepare, prepublish, and prepack scripts during the fetch phase, giving remote code execution without user approval. Publicly available exploit code exists (GitHub advisory GHSA-379q-355j-w6rj), but EPSS is low (0.11%) and the issue is not listed in CISA KEV; it is fixed in version 10.26.0.

Technical ContextAI

pnpm is a Node.js package manager whose v10 line introduced 'lifecycle scripts disabled by default' to mitigate supply-chain attacks: postinstall and similar build scripts only run for packages explicitly listed under onlyBuiltDependencies. This vulnerability is a CWE-693 (Protection Mechanism Failure) - the control is incomplete because it governs the install/build phase but not the git-fetch phase. When a dependency is specified via a git URL, pnpm clones and prepares it, and npm/pnpm semantics run prepare (and prepublish/prepack) scripts as part of producing an installable package from source. Those hooks execute outside the onlyBuiltDependencies gate, so attacker-controlled JavaScript in a git dependency's package.json scripts runs automatically. The affected CPE is cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:*:node.js:* across the 10.0.0-10.25 range.

RemediationAI

Vendor-released patch: pnpm 10.26.0 - upgrade pnpm to 10.26.0 or later, which closes the git-fetch-phase script execution path; this is the primary and recommended fix (see GHSA-379q-355j-w6rj and fix commit 73cc63504d9bc360c43e4b2feb9080677f03c5b5). Until you can upgrade, the highest-impact compensating control is to avoid git-hosted dependencies entirely and consume only registry-published, version-pinned packages, since the bypass is specific to the git fetch/prepare path; the trade-off is losing the ability to install packages directly from git. Where git dependencies are unavoidable, pin them to trusted commit SHAs, run pnpm install only inside sandboxed/ephemeral CI containers with no secrets and restricted network egress, and review the prepare/prepublish/prepack scripts in any git dependency's package.json before installing. Red Hat's VEX data (https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-69264.json) can confirm downstream package status.