AI Science Tracker

A project .npmrc can redirect nvm prefix cleanup to another file

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

Finding and attribution

When nvm use --delete-prefix invokes npm config delete, npm reads the project .npmrc first and may edit a user-selected config file. A malicious project can cause a victim’s config file to be rewritten or left world-writable; on a shared machine that can expose file contents or permit another local user to modify it. The advisory says project code does not run and the attacker chooses the target, not written bytes.

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

CVE identifiers: CVE-2026-121748.

AI and human contribution (source account): The nvm advisory explicitly credits Anthropic OSS Scanner (ANT-2026-WYRTKBQ5). Anthropic’s Oct 8 announcement says the scanner uses its strongest models, including Claude Mythos, and issues model-generated reports; exact model and workflow for this finding are not stated.

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-ccgf-7gv4-xg5h on Nov 4, 2026 and lists CVE-2026-121748. 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 prevents project .npmrc settings from selecting the config file that npm edits during prefix cleanup.

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: Low · highest recorded score 3.6. Documented technical effects: data modification.

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-121748: CVSS 4.0 · 1.8 (Low) · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N · Assessment scenarios: GENERAL. harborist (CNA; CVE Program record) · checked 16 Nov 2026.
  • CVE-2026-121748: CVSS 3.1 · 3.6 (Low) · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L · Assessment scenarios: GENERAL. harborist (CNA; CVE Program record) · checked 16 Nov 2026.

CVE-2026-121748: data modification.
Prerequisites / affected scope: A cloned repository/archive or local user in a writable shared parent can control project `.npmrc`; when a user runs `nvm use --delete-prefix`, npm may rewrite a selected config such as ~/.bashrc or make a global config world-writable. The attacker chooses the target but not written bytes, and no project code runs..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: nvm 0.41.0 prevents project .npmrc settings from selecting the config file that npm edits during prefix cleanup.

Original evidence

Download this source record (JSON)

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