Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade to nvm 0.41.0 or later, which removes an archive that fails verification instead of caching it.
Vendor Workaround
Until upgrading, after any "Checksums do not match" error, run `nvm cache clear` before using `nvm install --offline`.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 04 Nov 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.40.5 through 0.40.8, `nvm_download_artifact` downloads a release archive directly to its final path in `$NVM_DIR/.cache` and verifies its checksum afterwards; on a checksum mismatch it reports an error but leaves the rejected archive in place. A later `nvm install --offline` of the same version installs that cached file without a checksum, so an archive that was just rejected gets installed and its `node` and `npm` run. This gives code execution to a party who can alter the downloaded tarball (for example a poisoned CDN or cache object) but cannot also forge the `SHASUMS256.txt` beside it, if the victim runs `nvm install --offline` for that version after the visible "Checksums do not match" failure and before any online retry. Version 0.41.0 only puts an archive in the cache once its checksum has passed. | |
| Title | nvm install --offline installs a cached tarball that previously failed checksum verification | |
| Weaknesses | CWE-459 CWE-494 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: harborist
Published:
Updated: 2026-11-04T21:28:43.821Z
Reserved: 2026-11-03T23:39:03.684Z
Link: CVE-2026-121750
No data.
Status : Received
Published: 2026-11-04T22:17:54.873
Modified: 2026-11-04T22:17:54.873
Link: CVE-2026-121750
No data.
OpenCVE Enrichment
No data.