All posts

Nuxt 4.6.4 fixes eight advisories: upgrade, and check how your routes are protected.

Nuxt 4.6.4 fixes eight advisories: a leading // and an encoded %2F that can skip middleware and route rules, a dev-server file read, leaked error details and more.

Published
Reading time
8 min
By
Girish Babu GV

What happened#

Nuxt’s maintainers published eight advisories on 2 November 2026 and released nuxt@4.6.4 the same day. The npm registry shows nuxt@4.6.4 was published at 20:48 UTC on 2 November, after nitropack@2.13.6 at 17:09 UTC, and as I write it is still the registry’s latest nuxt. The release notes call it a security release, say it fixes eight advisories in Nuxt and updates nitropack to 2.13.6 for three more in Nitro, and recommend upgrading as soon as possible. Some of the advisories (for example the two I checked in GitHub’s global database) were reviewed there on 13 November, which is when they started surfacing in dependency tooling.

No advisory is rated above Moderate. Still, two of them are the kind that matter when a path is used as a gate: according to the advisories, the page that renders and the path the server-side checks see can disagree.

The eight advisories#

Nuxt advisories published 2 November 2026, as shown on the advisory pages
IssueIDSeverityAffected (Nuxt 4)
A leading // bypasses server/middleware and route rules on page routesCVE-2026-128077Moderate, 6.54.6.0 to 4.6.3
An encoded slash (%2F) bypasses route rules on catch-all pagesCVE-2026-128071Moderate, 6.54.0.0 to 4.6.3
Dev server serves files from a parent directory with a stray lockfile or workspace fileCVE-2026-128070Moderate, 5.9@nuxt/schema 3.5.0 to before 4.6.4
Message and data of unhandled server-render errors reach the clientCVE-2026-128075Moderate, 5.34.0.0 to 4.6.3
Webpack and rspack dev servers serve built source to DNS-rebinding pagesCVE-2026-128072Low, 3.14.0.0 to 4.6.3 (webpack or rspack builder only)
Payload URL generation has quadratic cost for repeated slashesCVE-2026-128074Low4.6.0 to 4.6.3
Wildcard redirect route rules in the experimental Vite server builder can redirect off-siteNo CVE listedLow, 3.1@nuxt/vite-server 4.6.0 to 4.6.3
Colliding island props can share one /__nuxt_island pathCVE-2026-128076Low, 3.14.4.6 to 4.6.3

In plain terms, per the advisories:

  • Leading //. Since 4.6.0, Nuxt treats a path that begins with // as a URL with a host before rendering, so //x/admin renders the page at /admin, while Nitro’s routing, route rules and server/middleware still see //x/admin. The advisory says an unauthenticated visitor can therefore reach a page that a path-keyed server check would have blocked, and that server-side redirect and headers rules (including a Content-Security-Policy) are skipped too. It says the fix for the earlier dot-segment advisory (4.6.3) did not cover this form. It does not affect server/api and server/routes handlers, route middleware set with definePageMeta, or Nuxt 3.x and 4.0 to 4.5.
  • Encoded slash. Route rules are matched with %2F left encoded, but the page router decodes it into route params. The advisory says a request such as /docs/internal%2Fguide can render a catch-all page without the rules for the path it resolves to, skipping redirect, headers, proxy and appMiddleware among others. It says static page routes and single-segment params are not affected, and neither are server/api and server/routes. Whether protected content leaks depends on how the page reads the route.
  • Dev-server file read. This affects only nuxt dev. When no workspace is declared, Nuxt could pick a parent directory as workspaceDir, and the Vite dev server allows /_nuxt/@fs/ requests for files under it. The advisory says both of these must hold: a stray lockfile or a settings-only pnpm-workspace.yaml or deno.json in a parent directory, and a dev server reachable from the network (--host, --tunnel, a published port or a proxy). Production builds are not affected.
  • Error details. In production, a non-HTTP error thrown while rendering was wrapped with createError and treated as deliberate, so its message and data could reach the client. For a failed $fetch, the advisory says that includes the requested URL with its query string, so a token in a URL could be exposed. A custom error.vue did not prevent it.
  • DNS rebinding. Only apps whose dev server uses the webpack or rspack builder; the default Vite builder rejects unknown hosts. The advisory says a malicious page could read built client chunks, and notes that Chromium’s Local Network Access prompts (Chrome 142 and later) limit exploitation. Private runtimeConfig is not in the client bundle, so it is not exposed.
  • Repeated slashes. A regular expression that strips trailing slashes is quadratic in the length of a run of slashes. The advisory says about 16,000 slashes cost roughly 0.1 to 0.4 seconds of synchronous CPU, and applies to SSR apps with an isr, swr or cache route rule, or with the opt-in experimental.early404.
  • Redirect rules. Only the experimental Vite server builder (server: { builder: 'vite' }) with a wildcard redirect whose target starts with ** or /**. A path such as /old//evil.example could produce a redirect to another origin. Rated Low, and it needs the visitor to click a link.
  • Island props. Affects apps that use <NuxtIsland> or server components and pass attacker-influenced strings as props. The advisory says different props could produce the same hash and so share one /__nuxt_island path, which matters for prerendering or for a CDN that caches that path while ignoring the query. Island hashes change after the fix.

Nitro. The Nitro 2.13.6 release notes name three advisories: cached handlers that might share entries across HTTP methods or replay per-user Set-Cookie headers (GHSA-39r7-wfcx-99xg), a proxy route-rule scope bypass via an empty // segment (GHSA-rhhp-7488-3qwf), and an open redirect via a backslash or control characters in wildcard redirect rules (GHSA-pqxc-r4h5-jc95). I read those from the release notes, not from the advisory pages, so I don’t quote their severity or version ranges.

Am I affected?#

Start with the version: anything on nuxt before 4.6.4 is on the affected side of at least some of these, and the exact range depends on the advisory (see the table). The conditions below narrow it down.

Does the issue apply to your app?
Look forThen check
routeRulesDo you use redirect, headers, proxy or cache rules keyed on a path prefix such as /admin/**? On 4.6.0 to 4.6.3, can //x/admin reach the page?
server/middlewareDoes a handler there check the request path to allow or deny access? Those checks are what the // bypass skips.
[...slug].vueDo you have catch-all pages or params that span segments, with rules or middleware on the paths they resolve to?
nuxt dev --hostIs your dev server reachable from the network (--host, --tunnel, a container port), and is there a lockfile or settings-only workspace file in a parent directory?
builder: 'webpack'Do you develop with the webpack or rspack builder? The default Vite builder is not affected by the DNS-rebinding issue.
$fetchIn production, can a failing server-side fetch throw with a URL that contains a token or other secret?
NuxtIslandDo islands receive user-controlled string props, and does a CDN cache /__nuxt_island by path alone?

What to do now#

  1. Find your versions. Check every Nuxt project, including monorepo packages and anything that bundles Nuxt.
  2. Upgrade to nuxt@4.6.4 or later. The release notes say @nuxt/nitro-server 4.5 and 4.6 accept several nitropack versions, so an existing lockfile may keep an older Nitro: check that nitropack resolves to 2.13.6 or later. (This detail comes from a third-party summary of the release notes; confirm it in your own lockfile.)
  3. Read the behaviour changes before deploying. The release notes list them: server-render error details are stripped unless they come from createError; cache, swr and isr rules only cache GET and HEAD and skip responses that set cookies or send private or no-store headers; wildcard proxy and redirect rules reject targets outside the rule’s scope; webpack and rspack dev servers reject unexpected Host headers unless listed in devServer.allowedHosts. If you develop behind a proxy or another hostname, add it there.
  4. If you can’t upgrade yet, use the advisories’ own workarounds: a server middleware that returns 404 for paths starting with // (or containing an encoded slash, narrowed to your protected prefixes), or a proxy or CDN that collapses repeated slashes; set workspaceDir explicitly and keep dev servers off untrusted networks.
  5. Rotate if you may have exposed secrets. The advisories say to treat files in a parent directory as exposed if a network-reachable dev server met the conditions, to rotate upstream tokens that may have appeared in error payloads, and to treat anything inlined into a development client bundle as exposed in the DNS-rebinding case.
Check, then update
# Which versions do you have (including nested ones)?
npm ls nuxt nitropack @nuxt/nitro-server @nuxt/schema

# Where do you key rules or checks on a path?
grep -rnE "routeRules|defineEventHandler" server nuxt.config.* 2>/dev/null

# Update, then confirm Nitro moved too
npm install nuxt@latest
npm ls nitropack

The advisories don’t say whether any of these has been exploited, and none lists indicators to look for. If you relied on route rules or server middleware for access control on a public app, a sensible precaution is to check your access logs for requests to protected pages that begin with // or contain %2F. That is my own suggestion, not advice from the advisories.

How I checked this site#

This site is a Next.js project on Vercel. I searched its package.json and package-lock.json for nuxt and nitro. The only matches are optional peer-dependency entries for nuxt in the lockfile, and there is no installed nuxt or nitropack package, so I found no dependency on either. That covers this repository only.

What the sources don’t say#

  • Whether anyone has exploited any of the eight. The advisories don’t say either way.
  • How many apps are in the affected configurations. The advisories give no numbers.
  • The full detail of the three Nitro advisories. I read their titles in the Nitro release notes, not the advisory pages, so I have no severity or affected ranges for them.
  • Why the release notes’ description of the workspace fix (a declared workspace root) differs slightly from the advisory’s (which also lists a git repository). Set workspaceDir explicitly if your layout is unusual.
  • I did not find news coverage. My independent checks are the npm registry and a third-party repository note that agrees on the counts; the rest comes from the Nuxt and Nitro projects themselves.

My take#

My own opinion, not from the advisories.

The two bypasses are the same lesson again: when a framework normalises a path for rendering and a different layer matches rules on the raw path, an attacker can pick the spelling that gets past the rule. If you can, put authorisation next to the data (inside the handler or the API route that returns it) rather than relying only on a path-keyed redirect or middleware, and test unusual spellings (//, %2F, dot segments) as part of your upgrade checks.

Sources#

Keep reading

Esc