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 3.4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Policies can require integrity verification of software prior to installation, reducing risks from unverified downloads.
Blocks installation of components lacking a valid signature, mitigating download or installation of code without integrity checks.
Acquisition and maintenance portions of the strategy drive requirements for integrity verification of downloaded or supplied code.
Mandating integrity control and approved-only changes during development prevents incorporation of code or components lacking integrity validation.
Supply chain protection requires integrity verification of acquired components, directly reducing insertion or tampering of malicious code during delivery.
Reduces exposure to code obtained without integrity verification by requiring assurance processes that confirm authenticity and absence of tampering.
Tamper resistance and detection commonly include integrity verification of code and firmware obtained from external sources.
Component authenticity requires verifying origin/integrity of acquired firmware or software, directly preventing inclusion of code without integrity checks.
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.
NVD Description
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.
Deeper analysisAI
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.
Details
- CWE(s)