pnpm: Repository-controlled configDependencies can select a pacquet native install engine (CVE-2026-55697)
A vulnerability in pnpm allows repository-controlled configDependencies to select and execute a native install engine called pacquet without proper trust validation. This can lead to execution of arbitrary native code during installation. The issue arises because pnpm treated pacquet or @pnpm/pacquet declared in pnpm-workspace.yaml as an install-engine opt-in, resolving and spawning platform-specific pacquet binaries from repository-controlled dependencies. A patch is available that restricts this behavior to trusted allowlists outside the repository.
AI Analysis
Technical Summary
pnpm versions before 10.34.2 and versions from 11.0.0 up to but not including 11.5.3 allow a repository to declare pacquet or @pnpm/pacquet as a configDependency in pnpm-workspace.yaml, which pnpm then installs and executes as a native install engine during command dispatch. The vulnerability stems from pnpm resolving and spawning platform-specific pacquet binaries from node_modules/.pnpm-config without verifying that the repository is trusted to select such an install engine. This can lead to arbitrary code execution with the privileges of the developer or CI user running pnpm. The patch restricts selection of pacquet install engines to trusted allowlists set outside the repository, preventing untrusted repository control over native install engines.
Potential Impact
An attacker controlling a repository can cause pnpm to execute arbitrary native code during dependency installation by specifying pacquet or @pnpm/pacquet as a configDependency. This can compromise the developer or CI environment with high confidentiality, integrity, and availability impact. The CVSS 3.1 score is 7.5 (High), reflecting network attack vector, high complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A patch is available and should be applied to affected pnpm versions. The patch restricts the selection of pacquet install engines to trusted allowlists configured outside the repository, preventing untrusted repository-controlled configDependencies from executing native install engines. Users should update to pnpm versions 10.34.2 or later, or 11.5.3 or later. No additional mitigation is required once patched.
pnpm: Repository-controlled configDependencies can select a pacquet native install engine (CVE-2026-55697)
Description
A vulnerability in pnpm allows repository-controlled configDependencies to select and execute a native install engine called pacquet without proper trust validation. This can lead to execution of arbitrary native code during installation. The issue arises because pnpm treated pacquet or @pnpm/pacquet declared in pnpm-workspace.yaml as an install-engine opt-in, resolving and spawning platform-specific pacquet binaries from repository-controlled dependencies. A patch is available that restricts this behavior to trusted allowlists outside the repository.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
pnpm versions before 10.34.2 and versions from 11.0.0 up to but not including 11.5.3 allow a repository to declare pacquet or @pnpm/pacquet as a configDependency in pnpm-workspace.yaml, which pnpm then installs and executes as a native install engine during command dispatch. The vulnerability stems from pnpm resolving and spawning platform-specific pacquet binaries from node_modules/.pnpm-config without verifying that the repository is trusted to select such an install engine. This can lead to arbitrary code execution with the privileges of the developer or CI user running pnpm. The patch restricts selection of pacquet install engines to trusted allowlists set outside the repository, preventing untrusted repository control over native install engines.
Potential Impact
An attacker controlling a repository can cause pnpm to execute arbitrary native code during dependency installation by specifying pacquet or @pnpm/pacquet as a configDependency. This can compromise the developer or CI environment with high confidentiality, integrity, and availability impact. The CVSS 3.1 score is 7.5 (High), reflecting network attack vector, high complexity, no privileges required, user interaction required, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A patch is available and should be applied to affected pnpm versions. The patch restricts the selection of pacquet install engines to trusted allowlists configured outside the repository, preventing untrusted repository-controlled configDependencies from executing native install engines. Users should update to pnpm versions 10.34.2 or later, or 11.5.3 or later. No additional mitigation is required once patched.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gj8w-mvpf-x27x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-55697"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a7e0349bf8831d5398f628b
Added to database: 08/13/2026, 17:47:53 UTC
Last enriched: 08/13/2026, 17:52:03 UTC
Last updated: 08/14/2026, 00:41:13 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.