CVE-2026-15921

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
3.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.32.1 through 0.40.5, nvm ls-remote (and other commands that refresh remote LTS aliases, such as nvm install --lts) parse the node.js mirror's index.tab and use each release's LTS codename field as an alias filename without validating it. A malicious, compromised, or man-in-the-middled mirror can return an LTS codename containing path-traversal sequences such as ../../../.bashrc, causing nvm to write the associated version string to a path outside $NVM_DIR/alias. With the default layout ($NVM_DIR is ~/.nvm), this can create or overwrite files in the user's home directory, including shell startup files, which can lead to code execution in a later shell session. Exploitation requires the victim to use a hostile mirror -- via a compromised mirror or CDN, a network man-in-the-middle, or a maliciously configured NVM_NODEJS_ORG_MIRROR/NVM_IOJS_ORG_MIRROR -- and to run an affected command. Version 0.40.6 validates remote LTS codenames as safe alias filenames and rejects .. path components when writing alias files.

CVSS v3
3.1
EG Score
3.1(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity31% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
13.2%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 16, 2026

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 07:07 UTCEG score recompute
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-15 21:24 UTCEG score recompute
  12. 2026-07-15 21:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15921?
CVE-2026-15921 is a low vulnerability published on July 15, 2026. Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.32.1 through 0.40.5, nvm ls-remote (and other commands that refresh remote LTS aliases, such as nvm install --lts) parse the node.js mirror's index.tab and use each release's LTS…
When was CVE-2026-15921 disclosed?
CVE-2026-15921 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15921 actively exploited?
CVE-2026-15921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15921?
CVE-2026-15921 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-15921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15921, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15921

Explore →

Is Your Infrastructure Affected by CVE-2026-15921?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.