# CVE-2026-119201: Nuxt dev server exposes generated appSecret through Vite file serving


- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-119201?

CVE-2026-119201 is a medium-severity vulnerability in nuxt, published on 29 Oct 2026. 

### Official description

Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, nuxt dev stores a generated appSecret in <buildDir>/app-secret, by default .nuxt/app-secret, within a directory allowed by Vite's server.fs configuration. A client with direct HTTP access to an exposed development server can fetch the file, use deriveSecret() to compute derived secrets such as the default useSession password, and forge session cookies accepted by that development server. The default localhost binding limits remote exposure, cross-origin browser reads are blocked, production builds and development servers with an explicitly configured appSecret are not affected. This issue is fixed in version 4.6.3.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2026-119201?


## How do I fix CVE-2026-119201?

No fix has been published for CVE-2026-119201 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119201 being exploited?

There is no known exploitation of CVE-2026-119201 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119201 and fix it if it is affected.

What it is: CVE-2026-119201 is a medium-severity vulnerability in nuxt, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119201 in the wild and no public exploit code.

Affected product: nuxt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119201/ (Markdown: https://insights.sbomify.com/CVE-2026-119201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119201
- OSV: https://osv.dev/vulnerability/CVE-2026-119201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119201/
Summaries are generated and may contain mistakes; the official description above is the record.