# CVE-2026-121747: nvm prints the contents of any readable file through a symlinked .nvmrc


- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-j6ch-mq5c-3h4x

## What is CVE-2026-121747?

CVE-2026-121747 is a medium-severity vulnerability in nvm-sh nvm, published on 4 Nov 2026. 

### Official description

Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.2.0 through 0.40.8, nvm does not check whether `.nvmrc` is a symbolic link. A repository or archive that ships `.nvmrc` as a symlink to another file (for example `../../.npmrc`, or `/proc/self/environ` on Linux) makes a plain `nvm use`, `nvm install`, `nvm which`, `nvm exec`, `nvm run`, or `nvm-exec` read that file and print its contents in the invalid-`.nvmrc` message (even with `--silent`) or, for a one-line file, in the `Found ... with version <...>` message; with the README's zsh `load-nvmrc` or bash `cdnvm` hook installed, entering the directory is enough. nvm sends the content nowhere; the attacker learns it only where they can see the victim's output, such as a CI log for a contributed branch. Version 0.41.0 still follows a symlinked `.nvmrc`, so deliberate links to another version file keep working, but never prints its content, and accepts it only if it contains a version or the name of an existing alias; the README's bash `cdnvm` hook, which read `.nvmrc` itself, now gets the version from nvm, so users of that hook must also update their copy of it.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following), CWE-59 (Improper Link Resolution Before File Access), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-121747 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121747 is a medium-severity vulnerability in nvm-sh nvm, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121747 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-121747/ (Markdown: https://insights.sbomify.com/CVE-2026-121747/index.md)
```

## Sources

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

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