AI Science Tracker

A symlinked .nvmrc can make nvm print a readable file

nvm (Node Version Manager) · AI involvement attributed to Anthropic OSS Scanner (model unspecified)

Finding and attribution

nvm read .nvmrc through symlinks and could print the target file contents in an invalid-version message or version display. A repository/archive can point .nvmrc at a readable file such as .npmrc; the attacker sees output only where the victim exposes it, such as a CI log or shared terminal. The advisory says this has the same outcome as CVE-2026-94185 through a different symlink mechanism, and is distinct from the separate --save write flaw CVE-2026-121746.

Product: nvm (Node Version Manager). AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and nvm maintainers.

CVE identifiers: CVE-2026-121747.

AI and human contribution (source account): The maintainer advisory directly credits Anthropic OSS Scanner (ANT-2026-G9REVGKT) and separately names an independent reporter. Anthropic’s Oct 8 scanner announcement identifies use of its strongest models, including Claude Mythos, and says reports are model-generated. The advisory does not specify which model produced this issue.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The nvm maintainer published GHSA-j6ch-mq5c-3h4x on Nov 4, 2026 and lists CVE-2026-121747. Public AI attribution is in the same item-level advisory; Anthropic’s Oct 8, 2026 scanner announcement is the provenance for the AI program, not the date of this case attribution.

Remediation status: fix documented. nvm 0.41.0 avoids printing the contents of a symlinked .nvmrc; users of the documented bash cd hook must also update that copied hook.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 4 Nov 2026. AI attribution dated 4 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 6.7. Documented technical effects: data disclosure.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-121747: CVSS 4.0 · 6.7 (Medium) · 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 · Assessment scenarios: GENERAL. harborist (CNA; CVE Program record) · checked 16 Nov 2026.
  • CVE-2026-121747: CVSS 3.1 · 5.5 (Medium) · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N · Assessment scenarios: GENERAL. harborist (CNA; CVE Program record) · checked 16 Nov 2026.

CVE-2026-121747: data disclosure.
Prerequisites / affected scope: A symlinked .nvmrc can make nvm print a readable file; disclosed data is limited to text nvm emits..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: nvm 0.41.0 avoids printing the contents of a symlinked .nvmrc; users of the documented bash cd hook must also update that copied hook.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases