Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, a client with TCP access to an exposed Nuxt development server can send a nuxt:dev:client-error event over the HMR socket with an absolute file path at the end of its message. The development server reads that file while building the client error report and returns its contents through the error overlay, development error channel, and terminal report, bypassing Vite's server.fs allow list. The default localhost binding limits remote exposure, cross-origin browser requests are rejected, production builds and Nuxt 3 are not affected, and no browser interaction is required. This issue is fixed in version 4.6.3.
CVE-2026-119198
MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.9 from GitHub Security Advisory (severity: MODERATE) published 2026-10-30. A secondary CVSS source baseline 5.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-113369 (ENISA EUVD) · GHSA-x287-wcfc-q46c (GitHub Security Advisories)Source: ENISA EUVD
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMhigh confidence
- EG Risk
- 27EG Risk 27/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)Severity59% × 45%Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 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 every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.3%
- EPSS %ILE
- 21st
- 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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-03). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 3, 2026
Advisory Details (4)
Auto-updated Oct 29, 2026Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)
Nuxt dev server arbitrary file read through client error reports · Advisory · nuxt/nuxt · GitHub
https://github.com/nuxt/nuxt/security/advisories/GHSA-x287-wcfc-q46cGitHub release Patch Available
v4.6.3
Patch available: nuxt/nuxt v4.6.3
https://github.com/nuxt/nuxt/releases/tag/v4.6.3GitHub commit
commit aec8129f68e9 (nuxt/nuxt)
Fix landed in nuxt/nuxt commit aec8129f68e9 — awaiting tagged release
https://github.com/nuxt/nuxt/commit/aec8129f68e9b870ca919f8f60e65a4608c8a6d8GitHub commit
commit 35856eb148bf (nuxt/nuxt)
Fix landed in nuxt/nuxt commit 35856eb148bf — awaiting tagged release
https://github.com/nuxt/nuxt/commit/35856eb148bf8d6f1ad753c5b8b337c52b4fd6b3Vendor Advisories for CVE-2026-119198(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | @nuxt/vite-builder @ 4.6.3 (fixes >= 4.6.0, < 4.6.3) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @nuxt/vite-builder | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 19× 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.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-03 17:26 UTCEchelonGraph re-scored
- 2026-11-03 17:26 UTCGHSA enrichmentGHSA-x287-wcfc-q46c · GitHub severity MODERATE · GitHub CVSS 5.9
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-03 16:33 UTCEchelonGraph re-scored
- 2026-11-03 16:33 UTCGHSA enrichmentGHSA-x287-wcfc-q46c · GitHub severity MODERATE · GitHub CVSS 5.9
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-30 17:27 UTCEchelonGraph re-scored
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
- 2026-10-29 21:27 UTCEchelonGraph re-scored
- 2026-10-29 21:02 UTCENISA EUVD ID recordedEUVD-2026-113369 · Source: ENISA EUVD
- 2026-10-29 20:21 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
- 2026-10-29 20:21 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownnpm:@nuxt/vite-builder
Frequently asked(5)
What is CVE-2026-119198?
CVE-2026-119198 is a medium-severity vulnerability; its CVE record was published on October 29, 2026. Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, a client with TCP access to an exposed Nuxt development server can send a nuxt:dev:client-error event over the HMR socket with an absolute file path at the end of its message. The development server reads that file…
When was the CVE record for CVE-2026-119198 published?
The CVE record for CVE-2026-119198 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 3, 2026; the record at its source may have been updated since.
Is CVE-2026-119198 actively exploited?
CVE-2026-119198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119198?
CVE-2026-119198 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119198?
A fix for CVE-2026-119198 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-119198 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-119198
Is Your Infrastructure Affected by CVE-2026-119198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.