CVE-2025-69263
Pnpm vulnerability
- Published7 Jan 2026
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. 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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2025-69263
- https://bugzilla.redhat.com/show_bug.cgi?id=2427703
- https://github.com/pnpm/pnpm/commit/0958027f88a99ccefe7e9676cdebba393dfbdc85
- https://github.com/pnpm/pnpm/security/advisories/GHSA-7vhp-vf5g-r2fw
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-69263.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-69263 being actively exploited?
CVE-2025-69263 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.47%.
How severe is CVE-2025-69263?
CVE-2025-69263 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.47% probability of exploitation.
Which products are affected by CVE-2025-69263?
Affected products include Pnpm.
How do I fix CVE-2025-69263?
Upgrade affected software to a fixed version, for example Pnpm 10.26.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-69263 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.