# CVE-2026-119199: Nuxt dev server exposes private runtime config through the Nitro dev bundle


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

## What is CVE-2026-119199?

CVE-2026-119199 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 3.0.0 until 4.6.3, the Nuxt development server can expose the Nitro 2 development bundle at <buildDir>/dev/index.mjs through Vite file serving when the server is reachable over HTTP. Nitro inlines private runtimeConfig values resolved at build time into that bundle, including secrets configured in nuxt.config, and Nuxt 4.6.0 and later also inline the generated development appSecret. The default localhost binding limits remote exposure, production builds and Nitro 3 are not affected, and runtime configuration supplied only through NUXT_* environment variables at server startup is not inlined. This issue is fixed in version 4.6.3.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-119199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119199 is a medium-severity vulnerability in nuxt, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119199 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-119199/ (Markdown: https://insights.sbomify.com/CVE-2026-119199/index.md)
```

## Sources

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

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