CVE-2025-69263
Published: 07 January 2026
Summary
CVE-2025-69263 is a high-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Pnpm Pnpm. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Software Dependencies and Development Tools (T1195.001); ranked at the 14.2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SA-12 (Supply Chain Protection) and SI-7 (Software, Firmware, and Information Integrity).
Deeper analysis
CVE-2025-69263 affects pnpm, a JavaScript package manager, in versions 10.26.2 and below. The vulnerability arises because these versions store HTTP tarball dependencies, as well as git-hosted tarballs, in the lockfile without integrity hashes. This design flaw enables the remote server hosting the tarball to deliver varying content across different installations, even when a lockfile is committed to version control, undermining the lockfile's intended reproducibility.
An attacker can exploit this by publishing a malicious package that includes an HTTP or git tarball dependency in its tree. Any victim who installs a package with such a dependency—regardless of a committed lockfile—may receive altered code tailored to the user, CI/CD environment, or timing. Exploitation requires no privileges (PR:N) but demands user interaction (UI:R) and high attack complexity (AC:H) over the network (AV:N), potentially yielding high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), with a CVSS v3.1 base score of 7.5. The associated CWE is CWE-494 (Download of Code Without Integrity Check).
The issue is addressed in pnpm version 10.26.0. Official mitigation details are available in the pnpm security advisory at https://github.com/pnpm/pnpm/security/advisories/GHSA-7vhp-vf5g-r2fw and the fixing commit at https://github.com/pnpm/pnpm/commit/0958027f88a99ccefe7e9676cdebba393dfbdc85. Security practitioners should upgrade to the patched version and audit dependencies for HTTP or git tarballs.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1190
Vulnerability details
pnpm is a package manager. Versions 10.26.2 and below store HTTP tarball dependencies (and git-hosted tarballs) in the lockfile without integrity hashes. This allows the remote server to serve different content on each install, even when a lockfile is committed.…
more
An attacker who publishes a package with an HTTP tarball dependency can serve different code to different users or CI/CD environments. The attack requires the victim to install a package that has an HTTP/git tarball in its dependency tree. The victim's lockfile provides no protection. This issue is fixed in version 10.26.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability enables supply chain compromise via unhashed tarball dependencies in pnpm lockfiles (CWE-494), allowing attackers to deliver variable malicious content to victims installing affected packages.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires verification of software/firmware integrity (via hashes or signatures) before installation or execution, blocking the CVE's core flaw of accepting unsigned HTTP/git tarballs.
Mandates supply-chain protections that include integrity validation of acquired components, preventing an attacker-controlled tarball from delivering varying malicious content across installs.
Requires use of signed components, which would have forced integrity metadata into the lockfile and eliminated the reproducibility bypass for HTTP tarball dependencies.