CVE-2023-54418

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-18. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2023-60734 (ENISA EUVD) · GHSA-9qm4-jxp8-3jmc (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nuxt 3.0.0-rc.1 before 3.0.0-rc.13 contains an arbitrary file read vulnerability caused by the Vite dev server default setting vite.server.fs.strict=false. Unauthenticated attackers can request /_nuxt/@fs/ with a raw query to read arbitrary files like /etc/passwd from the system. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

November 18, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
Patch available. Sources: github_commit, github_pr.
Web page

Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev Server | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nuxt-3.0.0-rc.1-3.0.0-rc.13-unauthenticated-arbitrary-file-read-via-vite-dev-server
Web page

nuclei-templates/http/vulnerabilities/nuxt/nuxt-js-lfi.yaml at main · projectdiscovery/nuclei-templates · GitHub

https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/nuxt/nuxt-js-lfi.yaml
GitHub commit

commit 44b4100e4c9c (nuxt/nuxt)

Fix landed in nuxt/nuxt commit 44b4100e4c9c — awaiting tagged release

https://github.com/nuxt/nuxt/commit/44b4100e4c9c4824c5484bc2571450d81cc85a12
GitHub pull request Patch Available

fix(vite): enable fs strict mode

Patch available: nuxt/framework v3.0.0-rc.13 (PR #8674 merged 2022-11-03)

https://github.com/nuxt/framework/pull/8674

Vendor Advisories for CVE-2023-54418(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-21 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-20 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-20 00:02 UTCEchelonGraph re-scored
  4. 2026-11-20 00:02 UTCGHSA enrichmentGHSA-9qm4-jxp8-3jmc · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-19 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-11-18 18:47 UTCEchelonGraph re-scored
  7. 2026-11-18 18:47 UTCGHSA enrichmentGHSA-9qm4-jxp8-3jmc · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-18 17:03 UTCENISA EUVD ID recordedEUVD-2023-60734 · Source: ENISA EUVD
  9. 2026-11-18 16:28 UTCEchelonGraph re-scored
  10. 2026-11-18 15:43 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  11. 2026-11-18 15:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2023-54418?
CVE-2023-54418 is a high-severity vulnerability; its CVE record was published on November 18, 2026. Nuxt 3.0.0-rc.1 before 3.0.0-rc.13 contains an arbitrary file read vulnerability caused by the Vite dev server default setting vite.server.fs.strict=false. Unauthenticated attackers can request /_nuxt/@fs/<absolute path> with a raw query to read arbitrary files like /etc/passwd from the system.…
When was CVE-2023-54418 made public?
CVE-2023-54418 was made public on May 4, 2023: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2023-54418 actively exploited?
CVE-2023-54418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-54418?
CVE-2023-54418 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2023-54418?
A fix for CVE-2023-54418 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54418 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-54418

Explore →

Is Your Infrastructure Affected by CVE-2023-54418?

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