# Nuxt dev server exposes generated appSecret through Vite file serving

Advisory record · `GHSA-3xf4-9g3c-4h4w`

- **Identifiers:** `GHSA-3xf4-9g3c-4h4w` · `CVE-2026-119201`
- **State:** Confirmed
- **Severity:** CVSS 4.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-552](https://cwe.mitre.org/data/definitions/552.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Oct 2026, 23:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `@nuxt/vite-builder` (npm): affected `>=4.6.0, <4.6.3`; fixed in `4.6.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The @nuxt/vite-builder package, versions 4.6.0 before 4.6.3, let the Nuxt dev server serve a generated development secret file (app-secret in the build directory) through Vite's file serving when no appSecret is configured. An attacker with direct HTTP access to a dev server exposed to a network can read the file and derive secrets from it, including the default useSession password, and forge session cookies accepted by that server. Upgrade @nuxt/vite-builder to 4.6.3, which denies access to the file; setting NUXT_APP_SECRET to a random value of at least 32 characters is an alternative.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:32 UTC: First seen by agentprime
- 31 Oct 2026, 13:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3xf4-9g3c-4h4w)

## Sources

- [GitHub Advisory Database: GHSA-3xf4-9g3c-4h4w](https://github.com/advisories/GHSA-3xf4-9g3c-4h4w)
- [OSV: GHSA-3xf4-9g3c-4h4w](https://osv.dev/vulnerability/GHSA-3xf4-9g3c-4h4w)
- <https://github.com/nuxt/nuxt/security/advisories/GHSA-3xf4-9g3c-4h4w>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-119201>
- <https://github.com/nuxt/nuxt/commit/2981290f36d9c5412c022758f3d89ba21a845308>
- <https://github.com/nuxt/nuxt/commit/545004cc350be7003dea4116ce6206d6f980b1fd>
- <https://github.com/nuxt/nuxt>
- <https://github.com/nuxt/nuxt/releases/tag/v4.6.3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3xf4-9g3c-4h4w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3xf4-9g3c-4h4w/>. Everything for agents: <https://agentprime.io/llms.txt>.