Skip to main content

pnpm Lockfile Integrity Bypass Allows Remote Dynamic Dependencies (CVE-2025-69263)

0
High
Published: 08/13/2026 (08/13/2026, 17:28:25 UTC)
Source: GCVE Database
Product: pnpm

Description

pnpm versions 10.26.2 and below have a vulnerability where HTTP and git-hosted tarball dependencies are stored in the lockfile without integrity hashes. This allows a remote server to serve different code on each install, bypassing lockfile protections. An attacker publishing a package with such dependencies can serve varying code to different users or CI/CD environments. The issue is fixed starting from version 10.26.0.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected software

Homebrewmore threats →ghsa
pnpm
pkg:brew/pnpm
Affected versions
<11.21.0

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

AILast updated: 10/04/2026, 21:17:35 UTC

Technical Analysis

pnpm, a package manager, in versions 10.26.2 and earlier, stores HTTP tarball and git-hosted tarball dependencies in the lockfile without including integrity hashes. This design flaw enables a remote server hosting these tarballs to deliver different content on each installation, even when a lockfile is committed and used. Consequently, an attacker who publishes a package containing an HTTP tarball dependency can manipulate the code served to different users or continuous integration environments, circumventing the expected immutability of the lockfile. The vulnerability is addressed in pnpm version 10.26.0 and later.

Potential Impact

An attacker can serve different malicious code to different victims or environments by exploiting the lack of integrity verification for HTTP and git-hosted tarball dependencies in the pnpm lockfile. This undermines the security guarantees of the lockfile, potentially leading to remote code execution or supply chain compromise. The vulnerability affects all users who install packages with HTTP/git tarball dependencies using pnpm versions 10.26.2 and below.

Mitigation Recommendations

Upgrade pnpm to version 10.26.0 or later, where this vulnerability is fixed. The fix adds integrity hashes for HTTP and git-hosted tarball dependencies in the lockfile, preventing remote content manipulation. No other mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BREW-pnpm-CVE-2025-69263
Osv Schema Version
1.7.3
Ecosystems
["Homebrew"]
Cvss Version
3.1

Threat ID: 6ac2c0b22cdf04f656523915

Added to database: 10/04/2026, 21:10:10 UTC

Last enriched: 10/04/2026, 21:17:35 UTC

Last updated: 10/04/2026, 21:17:35 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses