Nuxt: Dot segments in the request path bypass `server/middleware` path checks and server route rules on page routes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.6.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Nuxt, an open-source Vue.js web framework, is affected when its page routes are reached via dot-segment paths (literal or percent-encoded). Attackers can bypass server middleware checks, route rules, and per-route security headers, potentially accessing protected pages and their server-rendered data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.3, Nuxt resolves literal or percent-encoded dot segments before rendering a page while Nitro routing, server/middleware checks, and server route rules evaluate the unresolved path. A request such as /%2e/admin can therefore render app/pages/admin.vue and its server-rendered data while checks keyed to /admin, redirects, or per-route security headers do not apply. API handlers, appMiddleware, Nuxt 3, and Nuxt 4.0.0 through 4.5.x are not affected, and exploitation requires a client that sends dot segments without browser normalization. This issue is fixed in version 4.6.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- nuxt nuxt
From 4.6.0 · fixed in 4.6.3
- @nuxt nitro-server
From 4.6.0 · fixed in 4.6.3