medium

CVE

CVE-2026-126355, CVE-2026-126356, CVE-2026-126357, CVE-2026-126358, CVE-2026-126359, CVE-2026-126210, CVE-2026-126343, CVE-2026-128070, CVE-2026-128071, CVE-2026-128077, CVE-2026-128075, CVE-2026-128072, CVE-2026-128074, CVE-2026-128076, CVE-2026-126361, CVE-2026-126362, CVE-2026-126363, CVE-2026-126364

CWE

CWE-863, CWE-288, CWE-22, CWE-436, CWE-352, CWE-20, CWE-79, CWE-248, CWE-178, CWE-552

Affected Surface

  • npm `hono` before 4.13.16 (`CVE-2026-126358` RegExpRouter from 4.1.4, `CVE-2026-126357` mount, `CVE-2026-126355` csrf, `CVE-2026-126356` validator('form') from 4.5.1, `CVE-2026-126359` css helper from 3.12.0)
  • npm `@hono/node-server` before 1.19.18 and 2.0.0 to before 2.1.6 (`CVE-2026-126210` backslash path rewrite) and 2.0.0 to before 2.1.6 (`CVE-2026-126343` WebSocket upgrade crash)
  • npm `nuxt` / `@nuxt/schema` 3.5.0 to before 4.6.4, dev server only (`CVE-2026-128070`); Nuxt 3 is end of life and gets no fix
  • npm `astro` 5.14.3 to 7.4.6 with `@astrojs/node` (`CVE-2026-126364`), `astro` up to 7.4.4 (`CVE-2026-126361`), `@astrojs/svelte` 5.7.3 to 9.1.1 (`CVE-2026-126362`) and `@astrojs/solid-js` 0.2.0 to 7.1.1 (`CVE-2026-126363`)

Update, 16 November 2026 (six more Nuxt 4.6.4 CVEs): Nuxt 4.6.4, which this article already recommends, fixed more than the dev-server bug in section 5. Nuxt published six more advisories for it on 2 November. GitHub added CVE-2026-128077 to its reviewed database on 13 November and the other five on 16 November between 14:59 and 15:02 UTC. Two of them are unauthenticated route-protection bypasses rated 6.5: CVE-2026-128071 (/admin%2Fsecret skips route rules on catch-all pages) and CVE-2026-128077 (//x/admin skips serverHandlers, server/middleware, and redirect and headers rules on Nuxt 4.6.0 to 4.6.3). CVE-2026-128075 sends the message and data of unexpected server-render errors to the client in production, and for a failed $fetch that includes the full upstream URL and response body. Nuxt 3 is end of life and gets no fix for CVE-2026-128071, CVE-2026-128075, CVE-2026-128072 or CVE-2026-128076. Details are in section 5a and the table below.

TL;DR

GitHub published CVEs on 12 and 13 November 2026 for 12 advisories in four JavaScript web frameworks. The maintainers fixed them between 28 October and 5 November, so patched releases are already on npm. All are rated medium or low and none is reported as exploited. Hono and @hono/node-server each get roughly 100 million npm downloads a week, though, and three of the Hono bugs let an unauthenticated request skip auth middleware.

  1. Hono RegExpRouter skips wildcard middleware (CVE-2026-126358). The default SmartRouter usually picks RegExpRouter. It did not apply /admin/* middleware to a route registered as /admin*, did not match /api/:tenant{[^/]+}/admin/* against /api/:tenant/admin/:id, and let paths containing %0A, %0D, %E2%80%A8 or %E2%80%A9 reach the not-found handler with no wildcard middleware at all.
  2. Hono mount() path rewriting (CVE-2026-126357). For a dynamic mount like /api/:tenant/*, the prefix was cut by the length of the route pattern, so /api/a/xxxxx/admin/secret reached the mounted app as /admin/secret. Since 4.12.21, /app/public%5C..%5Cadmin/secret also collapsed to /admin/secret.
  3. Hono csrf() and validator('form'). Chromium’s <a ping> sends a credentialed cross-origin POST with Content-Type: text/ping, which csrf() never checked (CVE-2026-126355). A multipart/form-data; charset=utf-8 body passed an empty object to the form validator while the handler could still read every field (CVE-2026-126356).
  4. @hono/node-server backslash rewrite (CVE-2026-126210). The WHATWG URL parser turns /public\..\admin/secret into /admin/secret. nginx, HAProxy and Envoy keep the backslash, so a proxy rule that blocks /admin is bypassed.
  5. Nuxt dev server (CVE-2026-128070). A package-lock.json in your home directory (one npm install there is enough) could make Nuxt pick ~ as workspaceDir, and Vite then served GET /_nuxt/@fs/<home>/.ssh/id_ed25519. This needs the dev server to be reachable from the network (--host, --tunnel, a published container port).
  6. Astro. The /_image endpoint used by @astrojs/node compared paths case-insensitively (CVE-2026-126364), dynamic tag names allowed img/src/onerror=... (CVE-2026-126361), and the Svelte and Solid renderers didn’t escape slot names (CVE-2026-126362, CVE-2026-126363).

What to do now: upgrade to hono 4.13.16+, @hono/node-server 1.19.18+ or 2.1.6+, nuxt 4.6.4+, astro 7.4.7+, @astrojs/svelte 9.1.2+ and @astrojs/solid-js 7.1.2+. If you can’t upgrade Hono today, switch to new Hono({ router: new TrieRouter() }) and register auth middleware inside mounted apps. If a Nuxt dev server was ever exposed on a shared network, check parent directories for stray lockfiles and rotate SSH keys and cloud tokens in your home directory.

Affected packages

EcosystemPackageCVE (issue)SeverityAffected versionsFixed version
npmhonoCVE-2026-126358 (RegExpRouter skips wildcard middleware)Medium, CVSS 3.1 5.3>= 4.1.4, <= 4.13.154.13.16
npmhonoCVE-2026-126357 (mount() prefix stripping)Medium, CVSS 3.1 5.3< 4.13.164.13.16
npmhonoCVE-2026-126355 (csrf() ignores text/ping)Medium, CVSS 3.1 5.3< 4.13.164.13.16
npmhonoCVE-2026-126356 (validator('form') multipart parameters)Medium, CVSS 3.1 5.3>= 4.5.1, <= 4.13.154.13.16
npmhonoCVE-2026-126359 (css helper split </style>)Low, CVSS 3.1 3.4>= 3.12.0, <= 4.13.154.13.16
npm@hono/node-serverCVE-2026-126210 (backslash path rewrite)Medium, CVSS 3.1 5.3< 1.19.18; >= 2.0.0, < 2.1.61.19.18, 2.1.6
npm@hono/node-serverCVE-2026-126343 (WebSocket upgrade ECONNRESET crash)Medium, CVSS 3.1 5.3>= 2.0.0, < 2.1.62.1.6
npm@nuxt/schema (via nuxt)CVE-2026-128070 (dev server workspaceDir widening)Medium, CVSS 3.1 5.9>= 3.5.0, < 4.6.44.6.4; none for Nuxt 3
npmnuxt, @nuxt/nitro-server, @nuxt/vite-serverCVE-2026-128071 (%2F bypasses route rules on catch-all routes)Medium, CVSS 3.1 6.5nuxt >= 3.0.0, < 4.6.44.6.4; none for Nuxt 3
npm@nuxt/nitro-server (via nuxt)CVE-2026-128077 (leading // bypasses server handlers and route rules)Medium, CVSS 3.1 6.5>= 4.6.0, < 4.6.44.6.4
npmnuxtCVE-2026-128075 (unhandled error message and data sent to client)Medium, CVSS 3.1 5.3>= 3.0.0, < 4.6.44.6.4; none for Nuxt 3
npmnuxtCVE-2026-128074 (quadratic trailing-slash regex in payload URLs)Medium, no CVSS score>= 4.6.0, < 4.6.44.6.4
npm@nuxt/webpack-builder, @nuxt/rspack-builderCVE-2026-128072 (dev server serves client chunks after DNS rebinding)Low, CVSS 3.1 3.1>= 3.0.0, < 4.6.44.6.4; none for Nuxt 3
npmnuxt, @nuxt/nitro-serverCVE-2026-128076 (island props hash collision, incomplete fix for CVE-2026-46342)Low, CVSS 3.1 3.1>= 3.21.6, < 4.6.44.6.4; none for Nuxt 3
npmastro (with @astrojs/node)CVE-2026-126364 (/_image case-insensitive path check)Medium, CVSS 4.0 6.3astro >= 5.14.3, <= 7.4.6astro 7.4.7
npmastroCVE-2026-126361 (dynamic tag name XSS)Low, CVSS 4.0 2.3<= 7.4.47.4.5
npm@astrojs/svelteCVE-2026-126362 (slot name XSS)Low, CVSS 4.0 2.3>= 5.7.3, <= 9.1.19.1.2
npm@astrojs/solid-jsCVE-2026-126363 (slot name XSS)Low, CVSS 4.0 2.3>= 0.2.0, <= 7.1.17.1.2

Technical analysis

1. Hono RegExpRouter: middleware coverage decided at registration time (CVE-2026-126358)

RegExpRouter works out at registration time which wildcard middleware covers which route. It treated patterns that match the same requests as different, and its compiled wildcard didn’t match line terminators. An app like this was exposed:

import { Hono } from 'hono'
import { bearerAuth } from 'hono/bearer-auth'

const app = new Hono()                       // SmartRouter -> RegExpRouter
app.use('/admin/*', bearerAuth({ token }))
app.get('/admin*', (c) => c.text(secrets))   // GET /admin/x runs without bearerAuth

The advisory lists three cases: an explicit default parameter pattern only on the middleware side (since 4.13.0), /admin* routes next to /admin/* middleware (since 4.1.4), and an encoded line terminator in the path (since 4.4.0). In the third case, no wildcard matched, so the request fell through to the not-found handler without any wildcard middleware. That matters if notFound does something sensitive or if a catch-all route sits behind it. TrieRouter, LinearRouter and PatternRouter applied the middleware correctly in all three cases, which is why TrieRouter is the documented workaround. The fix (commit 8a103aa5) derives coverage from path structure and rejects custom patterns that can match the empty string, such as {[0-9]*}, with UnsupportedPathError. You have to regenerate PreparedRegExpRouter data after upgrading.

2. Hono mount(): prefix length taken from the pattern, not the match (CVE-2026-126357)

Before 4.13.16, app.mount() stripped the prefix with a fixed length:

-    replaceRequest ||= (() => {
-      const mergedPath = mergePath(this._basePath, path)
-      const pathPrefixLength = mergedPath === '/' ? 0 : mergedPath.length
-      return (request) => {
-        const url = new URL(request.url)
-        url.pathname = this.getPath(request).slice(pathPrefixLength) || '/'
-        return new Request(url, request)
-      }
-    })()
+    const mergedPath = mergePath(this._basePath, path)
+    const defaultReplaceRequest = (c: Context): Request =>
+      createMountedRequest(c, mergedPath.replace(/\/$/, ''), mergePath(mergedPath, '*'))

/api/:tenant is 12 characters, so /api/a/xxxxx/admin/secret minus its first 12 characters is /admin/secret. The outer app routes on the original path, so middleware on /api/:tenant/admin/* never runs, while the mounted app sees a request for /admin/secret. The old code also assigned the decoded path to url.pathname, which re-normalizes it: a decoded \ becomes / and .. collapses. The new createMountedRequest (commit 34f90432) strips the prefix segment by segment from the raw pathname, using the matched parameter values. Duplicate parameter names and patterns like /assets* now throw.

3. Hono csrf() and validator('form')

csrf() only checked Origin and Sec-Fetch-Site for content types an HTML form can send, on the assumption that anything else needs a CORS preflight. Chrome and Edge send <a ping> hyperlink-auditing requests as credentialed POSTs with Content-Type: text/ping and no preflight. Commit bf164719 adds text/ping to the list:

-const isRequestedByFormElementRe =
-  /^\b(application\/x-www-form-urlencoded|multipart\/form-data|text\/plain)\b/i
+const isCsrfContentTypeRe =
+  /^\b(application\/x-www-form-urlencoded|multipart\/form-data|text\/(?:plain|ping))\b/i

The body of a ping is fixed, so only endpoints whose effect is chosen by path or query string (logout, delete by ID, toggles) are reachable. The session cookie must also be sent cross-site: either the attacker page is same-site or the cookie uses SameSite=None. Firefox doesn’t send pings by default.

validator('form') matched multipart/form-data with a strict pattern that allowed only a single boundary parameter. multipart/form-data; charset=utf-8; boundary=... failed that check, so the validator callback got {}. A callback that accepts an empty object passed, and the handler could still read every field through c.req.parseBody().

4. @hono/node-server: proxy and app disagree on \ (CVE-2026-126210)

@hono/node-server handed the raw request-target to the WHATWG URL parser, which treats \ as / in special schemes and then resolves ... RFC 3986-style proxies forward the backslash as an ordinary character:

GET /public\..\admin/secret HTTP/1.1
nginx location /admin { deny all; }   -> path does not start with /admin, forwarded
@hono/node-server                     -> c.req.path === "/admin/secret"

Since 1.19.18 and 2.1.6, a raw backslash in the path gets 400 Bad Request for HTTP/1.1, HTTP/2, absolute-form targets and WebSocket upgrades (commit 3868998a). Access control inside the Hono app runs on the rewritten path, so /admin/* middleware in the app still applies. The bypass only affects rules enforced in front of the app. The companion bug, CVE-2026-126343, crashed the process when a client reset the TCP connection while async middleware was handling a WebSocket upgrade, because the socket had no error listener yet.

5. Nuxt: a stray lockfile widens Vite’s server.fs.allow (CVE-2026-128070)

Nuxt used pkg-types’ findWorkspaceDir to set its default workspaceDir, and the Vite dev server allows /_nuxt/@fs/ reads for anything under that directory. Outside a git repository, the farthest parent with any lockfile counted as the workspace. So did any pnpm-workspace.yaml or deno.json, even one that only held settings. Commit 89d3306d replaces it with a resolver that requires a real workspace declaration:

const WORKSPACE_FILES: Array<[file: string, declaresWorkspace?: RegExp]> = [
  ['pnpm-workspace.yaml', /^packages\s*:/m],
  ['lerna.json'],
  ['turbo.json'],
  ['rush.json'],
  ['deno.json', DECLARES_DENO_WORKSPACE_RE],
  ['deno.jsonc', DECLARES_DENO_WORKSPACE_RE],
]

A package.json with workspaces or a .git/config also counts. A lockfile on its own no longer does. The advisory’s example is ~/package-lock.json plus a project at ~/projects/app with no .git, started with nuxt dev --host. A plain HTTP client can then read ~/.ssh/id_ed25519, cloud credentials and the DevTools token in ~/.nuxt/devtools/dev-auth-token.txt. Production builds are not affected, and Nuxt 3 will not be patched.

5a. Nuxt 4.6.4: route rules matched a different path than the page router

Both route-rule bypasses come from the same mismatch. Route rules and server middleware look at one form of the request path, and the page router renders from another. For CVE-2026-128071, rules were matched with %2F still encoded while the router decoded it into a catch-all parameter. With app/pages/[...slug].vue and '/admin/**': { redirect: '/login' }, a request for /admin%2Fsecret was rendered and never redirected. For CVE-2026-128077, Nuxt 4.6.0 started parsing a path beginning with // as a URL with a host, so //x/admin rendered app/pages/admin.vue while Nitro’s handlers and rules saw //x/admin. The advisory’s example is a guard registered with serverHandlers: [{ route: '/admin', middleware: true, ... }]. It returns 401 for /admin and does nothing for //x/admin. In both cases a plain link works, because browsers send the path as written. Neither bug reaches server/api or server/routes handlers.

The 4.6.4 fix resolves route rules for both the raw path and the path with each %2F read as a separator, and applies the rules matched by either. On Nuxt 3, where there is no fix for CVE-2026-128071, the advisory’s workaround is a server middleware that returns 404 for page paths containing %2f (case-insensitive), or a proxy that rejects or decodes encoded slashes before forwarding.

6. Astro

CVE-2026-126364 is narrow. The /_image endpoint that @astrojs/node uses checked that a local image sat inside the build output with a case-insensitive comparison. On Linux, /_image?href=/../../DIST/client/secret.png&w=32&f=png resolved to /srv/app/DIST/client/secret.png when a case-variant sibling of dist/client existed. The attacker can’t create that directory, and only files the image service accepts can be read. The fix is in astro 7.4.7, so upgrading @astrojs/node alone doesn’t help. CVE-2026-126361 hits apps that let request data choose an element name (const Tag = Astro.url.searchParams.get('as')): img/src/onerror=alert(1) became an <img> with an onerror handler. The two renderer bugs wrote slot names into <astro-slot name="..."> without escaping; they are the Svelte and Solid versions of CVE-2026-50146 in Astro core.

Exposure indicators

There are no network IOCs; these are framework bugs. Request shapes to look for in access logs:

  • Paths containing %0A, %0D, %E2%80%A8 or %E2%80%A9 that hit routes behind wildcard middleware (CVE-2026-126358)
  • Paths under a dynamic mount whose first parameter segment has an unusual length, or that contain %5C..%5C (CVE-2026-126357)
  • Raw \ in the request path reaching a Node.js Hono server (CVE-2026-126210)
  • POST requests with Content-Type: text/ping (CVE-2026-126355)
  • GET /_nuxt/@fs/ requests for paths outside the project, especially .ssh, .aws, .config/gcloud or .nuxt/devtools (CVE-2026-128070)
  • /_image?href= values with .. and upper-case directory names (CVE-2026-126364)
  • Page requests whose path contains %2F under a protected prefix (CVE-2026-128071) or starts with // (CVE-2026-128077) and returns 200 where the plain path redirects or returns 401

Detection and remediation

Check what each project resolves:

npm ls hono @hono/node-server astro @astrojs/node @astrojs/svelte @astrojs/solid-js nuxt @nuxt/schema
grep -nE '"node_modules/(hono|@hono/node-server|astro|@astrojs/(node|svelte|solid-js)|nuxt|@nuxt/schema)"' -A2 package-lock.json | grep '"version"'
pnpm why hono   # or: yarn why hono

Upgrade:

npm install hono@^4.13.16 @hono/node-server@^2.1.6   # or @hono/node-server@^1.19.18 on the 1.x line
npm install astro@^7.4.7 @astrojs/svelte@^9.1.2 @astrojs/solid-js@^7.1.2
npx nuxi upgrade                                      # Nuxt 4.6.4+

If you can’t upgrade Hono yet:

  • Use new Hono({ router: new TrieRouter() }) (import from hono/router/trie-router) for apps that put auth on wildcard middleware.
  • Register auth middleware inside each mounted app rather than on the outer path.
  • Add a middleware before csrf() that rejects Content-Type: text/ping, or set session cookies to SameSite=Strict.
  • Make validator('form') callbacks reject an empty object, or validate await c.req.parseBody() in the handler.
  • For @hono/node-server, have the reverse proxy or WAF reject requests with a raw \ in the path, or move the path rule into Hono middleware, which sees the rewritten path.

For Nuxt, set workspaceDir explicitly in nuxt.config.ts and look for stray lockfiles above your projects:

ls -la ~/package-lock.json ~/pnpm-lock.yaml ~/yarn.lock ~/bun.lock ~/pnpm-workspace.yaml ~/deno.json 2>/dev/null

If a Nuxt dev server ran with --host, --tunnel or a published port while one of those files existed, rotate SSH keys, cloud CLI credentials and anything else stored in that parent directory. The Hono, Astro and node-server bugs don’t expose stored secrets, so they don’t require credential rotation.

Timeline

  • 2026-10-28: @astrojs/svelte 9.1.2 and @astrojs/solid-js 7.1.2 released.
  • 2026-11-01 (02:31 UTC): Hono publishes its advisories; v4.13.16 is released at 03:10 UTC.
  • 2026-11-02: @hono/node-server 1.19.18 and 2.1.6, Nuxt 4.6.4 and astro 7.4.5 released; node-server and Nuxt publish their advisories.
  • 2026-11-05: astro 7.4.7 released with the /_image path check fix.
  • 2026-11-09: Astro publishes GHSA-r3h5-4585-7x3w and GHSA-mh32-jxcr-mh9f.
  • 2026-11-12 (21:28 to 23:31 UTC): GitHub adds the node-server, Astro renderer and Hono advisories to its reviewed database; CVE-2026-126210 reaches NVD.
  • 2026-11-13 (00:20 UTC): CVE-2026-126358, CVE-2026-126357 and CVE-2026-126364 published to NVD.
  • 2026-11-13 (18:11 to 18:39 UTC): GitHub adds the Nuxt and Astro core advisories; CVE-2026-128070 reaches NVD.
  • 2026-11-13 (19:32 UTC): GitHub adds Nuxt CVE-2026-128077 (GHSA-r99w-jh2x-3mg9).
  • 2026-11-16 (14:59 to 15:02 UTC): GitHub adds Nuxt CVE-2026-128071, CVE-2026-128072, CVE-2026-128074, CVE-2026-128075 and CVE-2026-128076. Nuxt had published all six on 2 November alongside 4.6.4.

References

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References