Project Subscriptions
No data.
No advisories yet.
Solution
Upgrade to nvm 0.41.0 or later.
Workaround
Until upgrading, do not run `nvm use --delete-prefix` in an untrusted project directory; remove the `prefix` setting from your own npmrc files by hand instead.
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.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. | |
| Title | nvm use --delete-prefix lets a project .npmrc choose which file npm rewrites or makes world-writable | |
| Weaknesses | CWE-73 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: harborist
Published:
Updated: 2026-11-04T21:29:25.656Z
Reserved: 2026-11-03T23:38:59.224Z
Link: CVE-2026-121748
No data.
Status : Received
Published: 2026-11-04T22:17:54.523
Modified: 2026-11-04T22:17:54.523
Link: CVE-2026-121748
No data.
OpenCVE Enrichment
No data.