Supply-chain code substitution via unhashed tarballs
Published Jan 7, 2026 · Updated Jan 7, 2026
Integrity bypass in pnpm before 10.26.0 allows remote attackers to substitute dependency code through HTTP or Git tarball installs. The tarball resolver records only the resolved URL in pnpm-lock.yaml and omits an integrity hash, so later installs accept changed bytes from that URL. Exploitation requires installation of a package whose dependency tree contains an HTTP or Git tarball, enabling targeted or time-varying code delivery.
Summary
What happened
Integrity bypass in pnpm before 10.26.0 allows remote attackers to substitute dependency code through HTTP or Git tarball installs. The tarball resolver records only the resolved URL in pnpm-lock.yaml and omits an integrity hash, so later installs accept changed bytes from that URL. Exploitation requires installation of a package whose dependency tree contains an HTTP or Git tarball, enabling targeted or time-varying code delivery.
The record
- CVE
- CVE-2025-69263
- Published
- Jan 7, 2026
- Updated
- Jan 7, 2026
- Vendor
- pnpm
- Product
- pnpm
- Classifications
- CWE-494, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2026CVE publishedPublication date reported by the CVE source.
- Jan 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 10.26.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- pnpm lockfile integrity bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo