CVE
Nuxt arbitrary file read via Vite dev server
Affects Nuxt 3.0.0-rc.1 through 3.0.0-rc.12 in dev mode. Fixed in 3.0.0-rc.13.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.0.0-rc.13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.0.0-rc.13.
Summary
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. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.0.0-rc.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2023-54418 (Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev Server), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2023-54418 (entry last updated 2026-11-18):
Affected:
- Nuxt nuxt: from 3.0.0-rc.1, fixed in 3.0.0-rc.13
Fixed versions: 3.0.0-rc.13.
Conditions (all must be true for the bug to be hit):
- Only affects dev mode (source: https://github.com/nuxt/framework/pull/8674)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2023-54418 is not listed as of cve.now's last read.
This KEV status is for CVE-2023-54418 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nuxt/framework/pull/8674
- https://github.com/nuxt/nuxt/commit/44b4100e4c9c4824c5484bc2571450d81cc85a12
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/nuxt/nuxt-js-lfi.yaml
- https://www.vulncheck.com/advisories/nuxt-3.0.0-rc.1-before-3.0.0-rc.13-unauthenticated-arbitrary-file-read-via-vite-dev-server
- https://www.vulncheck.com/advisories/nuxt-3.0.0-rc.1-3.0.0-rc.13-unauthenticated-arbitrary-file-read-via-vite-dev-server
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2023-54418
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2023-54418"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Nuxt nuxt
From 3.0.0-rc.1 · fixed in 3.0.0-rc.13
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2023-54418 |
| Record | NVD · CVE-2023-54418 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/nuxt/nuxt-js-lfi.yaml |
| Other links 4 | |
| Patch | GitHub · nuxt/framework · Pull request #8674 |
| Patch | GitHub · nuxt/nuxt · Commit 44b4100e |
| Link | vulncheck.com · advisories/nuxt-3.0.0-rc.1-before-3.0.0-rc.13-unauthenticated-arbitrary-file-read-via-vite-dev-server |
| Link | vulncheck.com · advisories/nuxt-3.0.0-rc.1-3.0.0-rc.13-unauthenticated-arbitrary-file-read-via-vite-dev-server |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2023-54418
Is CVE-2023-54418 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Vite dev server in affected Nuxt versions can be used without authentication to read arbitrary files from the machine running it.Source: github.com
Which versions are affected by CVE-2023-54418?
nuxt: from 3.0.0-rc.1 before 3.0.0-rc.13.Source: cve.now feed data
Am I affected, and how do I check?
Nuxt versions from 3.0.0-rc.1 up to but not including 3.0.0-rc.13 are in range. The source says the issue only has impact in dev mode. To check a project, look at the nuxt version in package.json or run npm ls nuxt.Source: github.com
How do I fix CVE-2023-54418?
Upgrade Nuxt to 3.0.0-rc.13 or later, which is the fixed version in the range data.Source: github.com