For your digest
nuxt, @nuxt/nitro-server: Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page rout…
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- nuxt (npm): from 4.6.0, before 4.6.3
- @nuxt/nitro-server (npm): from 4.6.0, before 4.6.3
The fix
nuxt (npm) fixed in 4.6.3
npmnpm install nuxt@4.6.3pnpmpnpm add nuxt@4.6.3yarnyarn add nuxt@4.6.3bunbun add nuxt@4.6.3Check what is installednpm ls nuxtPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency nuxt to 4.6.3 or the nearest later release, to fix CVE-2026-119200. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@nuxt/nitro-server (npm) fixed in 4.6.3
npmnpm install "@nuxt/nitro-server@4.6.3"pnpmpnpm add "@nuxt/nitro-server@4.6.3"yarnyarn add "@nuxt/nitro-server@4.6.3"bunbun add "@nuxt/nitro-server@4.6.3"Check what is installednpm ls @nuxt/nitro-serverPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @nuxt/nitro-server to 4.6.3 or the nearest later release, to fix CVE-2026-119200. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".