CVE-2026-121745: nvm · Invocation of Process Using Visible Sensitive Information
Affects nvmSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low : upgrade to 0.41.0 when convenient.
Data as of 5 Nov 2026, 00:16 UTC
Thin evidence
One scorer or none| CNA (harborist) | CVSS 4.0 | 2.0 |
|---|---|---|
| CNA (harborist) | CVSS 3.1 | 2.5 |
- Patch
- Available – fixed in 0.41.0
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade nvm to 0.41.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nvm-shnvm | Affected
| Fixed in
|
GitHubnvmpkg:github/nvmOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade nvm to version 0.41.0 or later, where the authorization header is no longer passed as a command-line argument but via stdin or a private config file, preventing token exposure. If upgrading is not immediately possible, avoid setting NVM_AUTH_HEADER on shared hosts or ensure /proc is mounted with hidepid= to restrict process argument visibility. Note that BusyBox wget does not support the private config file mitigation, so using curl or GNU Wget is recommended.
Description
Node Version Manager (nvm) versions 0.40.0 through 0.40.8 have a vulnerability where the authorization header set in NVM_AUTH_HEADER is passed as a visible command-line argument to curl or wget during downloads. This exposure allows other local users on the same machine to potentially read sensitive tokens via process listings. The issue is fixed in version 0.41.0, which changes the method of passing the header to avoid command-line exposure.