<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 09:29:17 +0000</lastBuildDate>
    <item>
      <title>GHSA-r99w-jh2x-3mg9 — Nuxt: Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path chec…</title>
      <link>https://db.gcve.eu/vuln/ghsa-r99w-jh2x-3mg9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/nitro-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Since `4.6.0`, Nuxt parses a request path that starts with `//` as a URL with a host before rendering a page, so `//x/admin` renders the page at `/admin`. Nitro&amp;#39;s routing, Nitro&amp;#39;s route rules and `server/middleware` see the path as `//x/admin`, so server-side checks keyed on `/admin` do not apply. The fix for [GHSA-9v7c-q64q-vv33](https://github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33) in `4.6.3` covered dot segments but not this form.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.&lt;/p&gt;
&lt;p&gt;A route-scoped server handler is skipped:&lt;/p&gt;
&lt;p&gt;```ts
// nuxt.config.ts
export default defineNuxtConfig({
  serverHandlers: [{ route: &amp;#39;/admin&amp;#39;, middleware: true, handler: &amp;#39;~~/server/admin-guard.ts&amp;#39; }],
})
```&lt;/p&gt;
&lt;p&gt;```ts
// server/admin-guard.ts
export default defineEventHandler((event) =&amp;gt; {
  if (!isAuthenticated(event)) {
    throw createError({ statusCode: 401 })
  }
})
```&lt;/p&gt;
&lt;p&gt;With this handler, `/admin` returns 401, but `//x/admin` and `///x/admin` render `app/pages/admin.vue` along with the data it fetches during server rendering. `server/middleware` that checks `event.path.startsWith(&amp;#39;/admin&amp;#39;)` is skipped in the same way.&lt;/p&gt;
&lt;p&gt;Server-side `redirect` and `headers` route rules are also skipped, so `&amp;#39;/admin/**&amp;#39;: { redirect: &amp;#39;/login&amp;#39; }` does not redirect `//x/admin/secret`, and per-route security headers such as `Content-Security-Policy` are not sent.&lt;/p&gt;
&lt;p&gt;Browsers send a path such as `//x/admin` as written, so a p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/nitro-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Since `4.6.0`, Nuxt parses a request path that starts with `//` as a URL with a host before rendering a page, so `//x/admin` renders the page at `/admin`. Nitro&amp;#39;s routing, Nitro&amp;#39;s route rules and `server/middleware` see the path as `//x/admin`, so server-side checks keyed on `/admin` do not apply. The fix for [GHSA-9v7c-q64q-vv33](https://github.com/nuxt/nuxt/security/advisories/GHSA-9v7c-q64q-vv33) in `4.6.3` covered dot segments but not this form.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can bypass server-side controls that match on the request path of a page route.&lt;/p&gt;
&lt;p&gt;A route-scoped server handler is skipped:&lt;/p&gt;
&lt;p&gt;```ts
// nuxt.config.ts
export default defineNuxtConfig({
  serverHandlers: [{ route: &amp;#39;/admin&amp;#39;, middleware: true, handler: &amp;#39;~~/server/admin-guard.ts&amp;#39; }],
})
```&lt;/p&gt;
&lt;p&gt;```ts
// server/admin-guard.ts
export default defineEventHandler((event) =&amp;gt; {
  if (!isAuthenticated(event)) {
    throw createError({ statusCode: 401 })
  }
})
```&lt;/p&gt;
&lt;p&gt;With this handler, `/admin` returns 401, but `//x/admin` and `///x/admin` render `app/pages/admin.vue` along with the data it fetches during server rendering. `server/middleware` that checks `event.path.startsWith(&amp;#39;/admin&amp;#39;)` is skipped in the same way.&lt;/p&gt;
&lt;p&gt;Server-side `redirect` and `headers` route rules are also skipped, so `&amp;#39;/admin/**&amp;#39;: { redirect: &amp;#39;/login&amp;#39; }` does not redirect `//x/admin/secret`, and per-route security headers such as `Content-Security-Policy` are not sent.&lt;/p&gt;
&lt;p&gt;Browsers send a path such as `//x/admin` as written, so a p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-r99w-jh2x-3mg9</guid>
    </item>
  </channel>
</rss>
