Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

Nuxt dev server arbitrary file read through client error reports

CVE-2026-119198GHSA-x287-wcfc-q46c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxt/vite-builder 4.6.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-119198: 0.29% estimated exploitation activity in the next 30 days; percentile 21.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A client that can connect to the dev server's HMR socket can send a `nuxt:dev:client-error` event whose message ends in an absolute file path. The dev server reads that file while building the error report, and its contents are returned in the error overlay, on the dev error channel, and in the report shown in the terminal.

Impact This affects the development server only; production builds contain none of this code. Affected versions are `4.6.0` to `4.6.2`. Reading the file requires TCP access to the dev server, so the default localhost bind limits this to local processes, which can usually read the same files directly. With the dev server exposed to a network (`nuxt dev --host`, `nuxt dev --tunnel`, or a proxy onto the dev port), anyone who can reach the port can read any file the dev process can read: SSH keys, `.env` files, cloud credentials and other files outside the project. The same path is refused by Vite's `server.fs` allow list over `/_nuxt/@fs/`; the client…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-x287-wcfc-q46c

  2. Revision 1 · created ·

    Published from ghsa record GHSA-x287-wcfc-q46c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-119198

Advisory: Nuxt dev server arbitrary file read through client error reports
IDs: CVE-2026-119198, GHSA-x287-wcfc-q46c
Record: https://patchnext.com/advisories/cve-2026-119198 (revision 2, source checked 31 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nuxt/vite-builder 4.6.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nuxt/vite-builder: affected >= 4.6.0, < 4.6.3; fixed in 4.6.3

## Suggested inspection (read-only)
- `npm ls @nuxt/vite-builder --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @nuxt/vite-builder.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x287-wcfc-q46c (GitHub-reviewed advisory GHSA-x287-wcfc-q46c lists affected ranges: npm @nuxt/vite-builder >=4.6.0 <4.6.3)
- Verified: https://osv.dev/vulnerability/GHSA-x287-wcfc-q46c (OSV record GHSA-x287-wcfc-q46c lists affected ranges: npm @nuxt/vite-builder >=4.6.0 <4.6.3 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…