# CVE-2026-1665: Command Injection in nvm via NVM_AUTH_HEADER in wget code path

> Attackers can execute arbitrary shell commands via unsanitized environment variables in nvm's wget download path, affecting developers using affected versions.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 30 Jan 2026

## What is CVE-2026-1665?

CVE-2026-1665 is a medium-severity command injection vulnerability in nvm-sh nvm, published on 29 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A command injection vulnerability exists in nvm (Node Version Manager) versions 0.40.3 and below. The nvm_download() function uses eval to execute wget commands, and the NVM_AUTH_HEADER environment variable was not sanitized in the wget code path (though it was sanitized in the curl code path). An attacker who can set environment variables in a victim's shell environment (e.g., via malicious CI/CD configurations, compromised dotfiles, or Docker images) can inject arbitrary shell commands that execute when the victim runs nvm commands that trigger downloads, such as 'nvm install' or 'nvm ls-remote'.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

No fix has been published for CVE-2026-1665 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1665 being exploited?

There is no known exploitation of CVE-2026-1665 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1665 and fix it if it is affected.

What it is: CVE-2026-1665 is a medium-severity command injection vulnerability in nvm-sh nvm, published on 29 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1665 in the wild and no public exploit code.

Affected product: nvm-sh nvm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1665/ (Markdown: https://insights.sbomify.com/CVE-2026-1665/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1665
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1665
- OSV: https://osv.dev/vulnerability/CVE-2026-1665

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1665/
Summaries are generated and may contain mistakes; the official description above is the record.