Skip to main content
VulnerabilityPublished Updated

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

Affects pnpmSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 10.26.0 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.26.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade pnpm to 10.26.0.

Affected software

ProductAffectedFixed in
Homebrewpnpmpkg:brew/pnpmOther threatsAffected
  • >=4.0.2 <10.26.0
Fixed in
  • 10.26.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and included starting from pnpm version 10.26.0. Users should upgrade to version 10.26.0 or later to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the official patch.

Description

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

References

Community reviews

Loading reviews…