pnpm: Missing Support for Integrity Check
CVE-2026-48995 is a high-severity missing support for integrity check vulnerability in pnpm, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected pnpm versions: < 10.33.4; >= 11.0.0, < 11.0.7. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of pnpm you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 4.8 | Medium | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
pnpm is a package manager. Prior to 10.33.4 and 11.0.7, a malicious codeload.github.com server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile. The lockfile does not store the hash of the dependencies from https://codeload.github.com. This means that if this server was compromised or a person's machine configuration was compromised, pnpm would download and install these dependencies. This vulnerability is fixed in 10.33.4 and 11.0.7.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Support for Integrity Check
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
How developers prevent this class of flaw
- Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.
- Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.
More Missing Support for Integrity Check vulnerabilities (CWE-353)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in pnpm
- 7.1 High severity
- 7.4 High severity
- 7.5 High severity
- 7.1 High severity
- 7.1 High severity
- 8.2 High severity
Recent Missing Support for Integrity Check vulnerabilities
- 8.7 High severity
- 7.1 High severity
- 9.1 Critical severity
- 7.3 High severity
- 8.1 High severity
- 7.3 High severity
Spotted an error? Tell us.