Quick answers
- Is CVE-2026-119200 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119200 being exploited in the wild.
- How severe is CVE-2026-119200?
- Medium severity, with a CVSS score of 6.5, published 29 October 2026.
- Which products and versions are affected?
- @nuxt/nitro-server (npm) >= 4.6.0, < 4.6.3, SEMVER:introduced=4.6.0,fixed=4.6.3; nuxt (npm) >= 4.6.0, < 4.6.3, SEMVER:introduced=4.6.0,fixed=4.6.3; Nuxt 4.6.0 to 4.6.2.
- Is there a fix for CVE-2026-119200?
- Yes. @nuxt/nitro-server (npm): upgrade to 4.6.3 or later; nuxt (npm): upgrade to 4.6.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119200 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119200?
- Check whether you run @nuxt/nitro-server (npm), nuxt (npm) or Nuxt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @nuxt/nitro-server (npm): upgrade to 4.6.3 or later
npm install @nuxt/nitro-server@4.6.3 - nuxt (npm): upgrade to 4.6.3 or later
npm install nuxt@4.6.3
Technical details
The vulnerability occurs because Nuxt resolves dot segments during page rendering but Nitro routing, server middleware, and route rules evaluate the unresolved path, creating a mismatch. Requests like /%2e/admin can render app/pages/admin.vue with its server-rendered data while security checks keyed to /admin do not apply. This affects Nuxt 4.6.0–4.6.2 but not earlier versions (4.5.x and below), Nuxt 3, or API handlers and appMiddleware, and requires a client that does not perform browser normalization on dot segments.
Affected products
- Nuxt Nuxt 4.6.0 to 4.6.2
Identifiers
- CVE-2026-119200
- GHSA-9v7c-q64q-vv33
Timeline
- 2026-10-29: disclosed
- 2026-10-27: patched