Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

Nuxt dev server exposes generated appSecret through Vite file serving

CVE-2026-119201GHSA-3xf4-9g3c-4h4w

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
4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-119201: 0.21% estimated exploitation activity in the next 30 days; percentile 10.49 (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.

Impact When no `appSecret` is configured (via `NUXT_APP_SECRET`, `NITRO_APP_SECRET` or `runtimeConfig.appSecret`), `nuxt dev` generates a development secret and stores it in ` /app-secret` (by default `.nuxt/app-secret`). The build directory is inside the directories that Nuxt passes to Vite's `server.fs.allow`, so the file can be fetched from the dev server: ```bash curl http:// /_nuxt/@fs/ /.nuxt/app-secret ``` Anyone who can read it can compute every secret derived from it with `deriveSecret()`, including the default password used by `useSession`, and so can forge session cookies accepted by that dev server. Exploitation requires direct HTTP access to the dev server. `nuxt dev` listens on localhost by default, so this mainly affects dev servers that are exposed to a network (for example with `--host`, a published container port or a tunnel). A malicious website cannot read the file through a developer's browser: Vite's CORS and host checks prevent pages on other origins from…

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

    Amended from osv record GHSA-3xf4-9g3c-4h4w

  2. Revision 1 · created ·

    Published from ghsa record GHSA-3xf4-9g3c-4h4w

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-119201

Advisory: Nuxt dev server exposes generated appSecret through Vite file serving
IDs: CVE-2026-119201, GHSA-3xf4-9g3c-4h4w
Record: https://patchnext.com/advisories/cve-2026-119201 (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 4.8)
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-3xf4-9g3c-4h4w (GitHub-reviewed advisory GHSA-3xf4-9g3c-4h4w lists affected ranges: npm @nuxt/vite-builder >=4.6.0 <4.6.3)
- Verified: https://osv.dev/vulnerability/GHSA-3xf4-9g3c-4h4w (OSV record GHSA-3xf4-9g3c-4h4w 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…