No analysis available yet.
Vendor Solution
Upgrade to nvm 0.41.0 or later.
Vendor Workaround
Until upgrading, check that `.nvmrc` is not a symlink (`ls -l .nvmrc`) before running `nvm use --save` or `nvm install --save` in an untrusted project directory.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 04 Nov 2026 21:45: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.0 through 0.40.8, `nvm use --save` and `nvm install --save` (or `-w`) write the resolved version to `$PWD/.nvmrc` with `tee`, which follows a symbolic link. A repository that commits `.nvmrc` as a symlink to a path outside itself (git recreates the link on clone) therefore makes `--save` truncate any file the user can write, such as a shell startup file or `~/.ssh/authorized_keys`, and replace its contents with the version string, or create the target of a dangling link; the link itself is left unchanged, so `git status` stays clean. The attacker does not control the content written, so this is data loss, not code execution. Version 0.41.0 refuses, with a warning, to write when `.nvmrc` in the current directory is a symlink, dangling or not, rather than writing through it or replacing it. | |
| Title | nvm use --save and nvm install --save write through a symlinked .nvmrc, overwriting any file the user can write | |
| Weaknesses | CWE-59 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: harborist
Published:
Updated: 2026-11-04T21:31:57.022Z
Reserved: 2026-11-03T23:38:59.223Z
Link: CVE-2026-121746
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-59
Improper Link Resolution Before File Access ('Link Following')