<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 08:56:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406469</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406469</link>
      <description>EUVD-2026-406469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406469</guid>
    </item>
    <item>
      <title>GHSA-f3x9-2chm-73c8 — Nuxt: Incomplete fix for GHSA-6gq8-jgmh-3ffp: an encoded slash (`%2F`) in the request path bypasses route rules on catc…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f3x9-2chm-73c8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt, npm: @nuxt/nitro-server, npm: @nuxt/vite-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Nuxt matches route rules against the request path with encoded slashes (`%2F`) left encoded, while the page router decodes them into route params. A request that spells a slash as `%2F` can therefore render a page through a catch-all route without the route rules configured for the path it resolves to. The fix for [GHSA-6gq8-jgmh-3ffp](https://github.com/nuxt/nuxt/security/advisories/GHSA-6gq8-jgmh-3ffp) deliberately left reserved escapes such as `%2F` encoded, so it did not cover this form.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can bypass route rules that protect paths served by a catch-all page route, or by a custom route whose param can span several segments.&lt;/p&gt;
&lt;p&gt;```ts
export default defineNuxtConfig({
  routeRules: {
    &amp;#39;/docs/internal/**&amp;#39;: { appMiddleware: &amp;#39;auth&amp;#39;, headers: { &amp;#39;X-Frame-Options&amp;#39;: &amp;#39;DENY&amp;#39; } },
    &amp;#39;/admin/**&amp;#39;: { redirect: &amp;#39;/login&amp;#39; },
  },
})
```&lt;/p&gt;
&lt;p&gt;With `app/pages/docs/[...slug].vue`, `/docs/internal/guide` runs `auth`, but `/docs/internal%2Fguide` renders the same page without running `auth` and without the header. With a root `app/pages/[...slug].vue`, `/admin%2Fsecret` is rendered instead of redirected.&lt;/p&gt;
&lt;p&gt;The rules skipped include server-side `redirect`, `headers`, `proxy`, `ssr` and `noScripts`, and `appMiddleware`, `appLayout` and `redirect` as matched in the app during server rendering and client navigation. `getRouteRules` returns the same incomplete result.&lt;/p&gt;
&lt;p&gt;Whether the page then shows protected content depends on how it reads the route:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt, npm: @nuxt/nitro-server, npm: @nuxt/vite-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Nuxt matches route rules against the request path with encoded slashes (`%2F`) left encoded, while the page router decodes them into route params. A request that spells a slash as `%2F` can therefore render a page through a catch-all route without the route rules configured for the path it resolves to. The fix for [GHSA-6gq8-jgmh-3ffp](https://github.com/nuxt/nuxt/security/advisories/GHSA-6gq8-jgmh-3ffp) deliberately left reserved escapes such as `%2F` encoded, so it did not cover this form.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can bypass route rules that protect paths served by a catch-all page route, or by a custom route whose param can span several segments.&lt;/p&gt;
&lt;p&gt;```ts
export default defineNuxtConfig({
  routeRules: {
    &amp;#39;/docs/internal/**&amp;#39;: { appMiddleware: &amp;#39;auth&amp;#39;, headers: { &amp;#39;X-Frame-Options&amp;#39;: &amp;#39;DENY&amp;#39; } },
    &amp;#39;/admin/**&amp;#39;: { redirect: &amp;#39;/login&amp;#39; },
  },
})
```&lt;/p&gt;
&lt;p&gt;With `app/pages/docs/[...slug].vue`, `/docs/internal/guide` runs `auth`, but `/docs/internal%2Fguide` renders the same page without running `auth` and without the header. With a root `app/pages/[...slug].vue`, `/admin%2Fsecret` is rendered instead of redirected.&lt;/p&gt;
&lt;p&gt;The rules skipped include server-side `redirect`, `headers`, `proxy`, `ssr` and `noScripts`, and `appMiddleware`, `appLayout` and `redirect` as matched in the app during server rendering and client navigation. `getRouteRules` returns the same incomplete result.&lt;/p&gt;
&lt;p&gt;Whether the page then shows protected content depends on how it reads the route:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f3x9-2chm-73c8</guid>
    </item>
  </channel>
</rss>
