CVE
Nuxt path check bypass in server middleware
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.6.4.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.27% · 19th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 40/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 26% of @nuxt/nitro-server downloads last week were affected versions (751K).npm, 2.9M downloads in the last 7 days, read Nov 15, 2026
- 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 and @nuxt/nitro-server are affected by a flaw where a request path starting with "//" bypasses server middleware path checks, route rules, and security headers meant for the real path. An attacker can send such a request remotely, without logging in, to reach pages like /admin without the protections configured for them.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Nuxt is an open-source web development framework for Vue.js. From 4.6.0 until 4.6.4, Nuxt parses a request path beginning with // as a URL host before rendering a page, while Nitro server/middleware and routeRules continue to evaluate the original path. An unauthenticated request such as //x/admin can therefore resolve to the /admin page without route-scoped serverHandlers, server/middleware path checks, redirects, or security headers configured for /admin. API handlers in server/api and server/routes, appMiddleware, page middleware are unaffected. This issue is fixed in version 4.6.4.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach16/20@nuxt/nitro-server: 2.7M downloads a week
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 4.6.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128077 (Nuxt: Incomplete fix for CVE-2026-119200: a leading `//` in the request path bypasses `server/middleware` path checks and server route…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128077 (entry last updated 2026-11-13):
Affected:
- nuxt nuxt: from 4.6.0, fixed in 4.6.4
- @nuxt nitro-server: from 4.6.0, fixed in 4.6.4
- npm package @nuxt/nitro-server: from 4.6.0, fixed in 4.6.4
Fixed versions: 4.6.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128077 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128077 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nuxt/nuxt/security/advisories/GHSA-r99w-jh2x-3mg9
- https://github.com/nuxt/nuxt/commit/75c12c6fb4c22ec2cbde0051da24776d2dffa868
- https://github.com/nuxt/nuxt/releases/tag/v4.6.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128077
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128077"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nuxt nuxt
From 4.6.0 · fixed in 4.6.4
- @nuxt nitro-server
From 4.6.0 · fixed in 4.6.4
From 4.6.0 · fixed in 4.6.4
Fixed in 4.6.4 (released Nov 2, 2026, 11 days before disclosure).
The latest release, 4.6.4, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128077
Is CVE-2026-128077 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-128077?
nuxt: from 4.6.0 before 4.6.4. nitro-server: from 4.6.0 before 4.6.4. @nuxt/nitro-server (npm): from 4.6.0 before 4.6.4.Source: cve.now feed data
How do I fix CVE-2026-128077?
Upgrade to a fixed version: 4.6.4.Source: cve.now feed data