nvm alias resolution follows `..` and discloses files outside $NVM_DIR/alias (CVE-2026-94185) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-94185

nvm alias resolution follows `..` and discloses files outside $NVM_DIR/alias

Answer in brief

CVE-2026-94185 records a Unknown severity vulnerability in nvm alias resolution follows `..` and discloses files outside $NVM_DIR/alias. The current sources do not mark it as known exploited. The current feed maps nvm-sh/nvm (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 21, 2026Updated Sep 21, 2026Source checked Sep 21, 2026First seen by HOL Sep 21, 2026Material review Sep 21, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nvm-sh/nvm (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nvm-sh/nvmgeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for nvm-sh/nvm.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 21, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

nvm resolves a requested version or alias by treating it as a filename under $NVM_DIR/alias. Before 0.40.8, nvm_alias() concatenated the requested name onto that directory and read the result with no containment check, so a name containing a `..` component escaped the alias directory; under the default layout an alias such as `../../.npmrc` resolves to a file in the user's home directory. nvm_print_alias_file() then emits every non-comment, non-empty line of whatever was opened. A version string taken from an untrusted .nvmrc reaches this path, so a developer who runs `nvm use`, `nvm install`, or `nvm which` inside an attacker-supplied repository discloses the first non-comment line of an arbitrary file readable by that user, in the resulting "is not yet installed" error message. A user-supplied `nvm alias <traversing-name>` discloses every non-comment line of the target file. There is no integrity or availability impact, and no command execution on this path.

Quoted source text, attributed separately from HOL analysis.