CVE-2026-118905

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-112603 (ENISA EUVD)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Harborist) states them: "Upgrade to nvm 0.40.6 or later."

Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.31.2 through 0.40.5, nvm_ls filters installed versions with a sed program that embeds the requested version pattern in a \#...# address, escaping . (and, since 0.40.4, #) but not backslash. A version string containing # (or \#) therefore closes the address early, and the rest of it is parsed as sed commands: with GNU sed, the e command runs a shell command as the user; with BSD sed, the w and r commands write and read files. This is reachable whenever an attacker-influenced version string is passed to nvm use, nvm which, nvm ls, nvm version, nvm run, or nvm exec, or to nvm-exec via NODE_VERSION, and at least one version is installed. nvm's own .nvmrc parser strips comments, so a bare nvm use is not affected; however, the bash cdnvm and zsh load-nvmrc auto-switch hooks documented in the README read .nvmrc as-is and pass it to nvm ls and nvm version, so a user with one of those hooks installed runs the attacker's command just by changing into a directory under a malicious .nvmrc; scripts that run nvm use "$(cat .nvmrc)" are affected the same way. Version 0.40.6 passes any version pattern containing # or a newline through the .nvmrc content parser first, so no # reaches the sed program.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 29, 2026

Last Modified

November 5, 2026

Advisory Details (4)

Auto-updated Nov 1, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Version pattern escaping in nvm_ls lets an untrusted version string inject sed commands · Advisory · nvm-sh/nvm · GitHub

https://github.com/nvm-sh/nvm/security/advisories/GHSA-vgqf-vc3m-4wv3
GitHub release Patch Available

v0.40.6

Patch available: nvm-sh/nvm v0.40.6

https://github.com/nvm-sh/nvm/releases/tag/v0.40.6
GitHub pull request Patch Available

[Fix] Parse commented nvmrc content in nvm_ls

Patch available: nvm-sh/nvm v0.40.6 (PR #3854 merged 2026-07-09)

https://github.com/nvm-sh/nvm/pull/3854
GitHub commit Patch Available

commit 82315e2b1895 (nvm-sh/nvm)

Patch available: nvm-sh/nvm v0.40.6 (contains commit 82315e2b1895)

https://github.com/nvm-sh/nvm/commit/82315e2b189528a006da6701eac30e8c364ffd22

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 16× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-11 03:44 UTCEchelonGraph re-scored
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-11-05 21:27 UTCEchelonGraph re-scored
  10. 2026-11-05 20:53 UTCEchelonGraph re-scored
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-11-03 20:14 UTCEchelonGraph re-scored
  14. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-29 06:26 UTCEchelonGraph re-scored
  20. 2026-10-29 06:01 UTCENISA EUVD ID recordedEUVD-2026-112603 · Source: ENISA EUVD
  21. 2026-10-29 05:28 UTCEchelonGraph re-scoredFirst assessed: 7.0 HIGH
  22. 2026-10-29 05:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-118905?
CVE-2026-118905 is a high-severity vulnerability; its CVE record was published on October 29, 2026. Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.31.2 through 0.40.5, nvm_ls filters installed versions with a sed program that embeds the requested version pattern in a \#...# address, escaping . (and, since 0.40.4, #) but not…
When was the CVE record for CVE-2026-118905 published?
The CVE record for CVE-2026-118905 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-118905 actively exploited?
CVE-2026-118905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118905?
CVE-2026-118905 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118905?
A fix for CVE-2026-118905 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Harborist) states them: "Upgrade to nvm 0.40.6 or later."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-118905?

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

Book a Demo →Browse All CVEs