<?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, 06 Oct 2026 00:41:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-293134</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-293134</link>
      <description>EUVD-2026-293134</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-293134</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41248</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41248</link>
      <description>&lt;p&gt;Clerk JavaScript is the official JavaScript repository for Clerk authentication. createRouteMatcher in @clerk/nextjs, @clerk/nuxt, and @clerk/astro can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers. This vulnerability is fixed in @clerk/astro 1.5.7, 2.17.10, and 3.0.15; @clerk/nextjs 5.7.6, 6.39.2, and 7.2.1; @clerk/nuxt 1.13.28 and 2.2.2; and @clerk/shared 2.22.1, 3.47.4, anc 4.8.1&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Clerk JavaScript is the official JavaScript repository for Clerk authentication. createRouteMatcher in @clerk/nextjs, @clerk/nuxt, and @clerk/astro can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers. This vulnerability is fixed in @clerk/astro 1.5.7, 2.17.10, and 3.0.15; @clerk/nextjs 5.7.6, 6.39.2, and 7.2.1; @clerk/nuxt 1.13.28 and 2.2.2; and @clerk/shared 2.22.1, 3.47.4, anc 4.8.1&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41248</guid>
    </item>
    <item>
      <title>GHSA-vqx2-fgx2-5wq9 — Official Clerk JavaScript SDKs: Middleware-based route protection bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vqx2-fgx2-5wq9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @clerk/nextjs, npm: @clerk/nuxt, npm: @clerk/astro, npm: @clerk/shared&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`createRouteMatcher` in `@clerk/nextjs`, `@clerk/nuxt`, and `@clerk/astro` can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers.&lt;/p&gt;
&lt;p&gt;Sessions are not compromised and no existing user can be impersonated - the bypass only affects the middleware-level gating decision.&lt;/p&gt;
&lt;p&gt;## Who is affected&lt;/p&gt;
&lt;p&gt;All apps using `createRouteMatcher` should upgrade to the patched versions. Patches are drop-in with no API changes. The information below describes the scope of the bypass and helps you understand whether you are potentially affected, but is not a reason to delay the upgrade.&lt;/p&gt;
&lt;p&gt;Apps relying only on middleware gating via `createRouteMatcher` are affected, because a crafted request can skip middleware checks and reach downstream handlers (API routes, server components, etc.). This middleware pattern permits the bypass:&lt;/p&gt;
&lt;p&gt;```ts
// Next.js example, equivalent patterns exist in Nuxt and Astro
const isProtectedRoute = createRouteMatcher([&amp;#39;/admin(.*)&amp;#39;]);&lt;/p&gt;
&lt;p&gt;export default clerkMiddleware(async (auth, req) =&amp;gt; {
  if (isProtectedRoute(req)) {
    await auth.protect();
  }
});
```&lt;/p&gt;
&lt;p&gt;That said, the bypass is limited to the middleware-level route-matching gate. `clerkMiddleware` still authenticates the request and `auth()` reflects the real authentication state of the caller. Auth checks performed inside your route handlers, server components, or server actions continue to work correctly and are not affected. Whether your app is affected…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @clerk/nextjs, npm: @clerk/nuxt, npm: @clerk/astro, npm: @clerk/shared&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`createRouteMatcher` in `@clerk/nextjs`, `@clerk/nuxt`, and `@clerk/astro` can be bypassed by certain crafted requests, allowing them to skip middleware gating and reach downstream handlers.&lt;/p&gt;
&lt;p&gt;Sessions are not compromised and no existing user can be impersonated - the bypass only affects the middleware-level gating decision.&lt;/p&gt;
&lt;p&gt;## Who is affected&lt;/p&gt;
&lt;p&gt;All apps using `createRouteMatcher` should upgrade to the patched versions. Patches are drop-in with no API changes. The information below describes the scope of the bypass and helps you understand whether you are potentially affected, but is not a reason to delay the upgrade.&lt;/p&gt;
&lt;p&gt;Apps relying only on middleware gating via `createRouteMatcher` are affected, because a crafted request can skip middleware checks and reach downstream handlers (API routes, server components, etc.). This middleware pattern permits the bypass:&lt;/p&gt;
&lt;p&gt;```ts
// Next.js example, equivalent patterns exist in Nuxt and Astro
const isProtectedRoute = createRouteMatcher([&amp;#39;/admin(.*)&amp;#39;]);&lt;/p&gt;
&lt;p&gt;export default clerkMiddleware(async (auth, req) =&amp;gt; {
  if (isProtectedRoute(req)) {
    await auth.protect();
  }
});
```&lt;/p&gt;
&lt;p&gt;That said, the bypass is limited to the middleware-level route-matching gate. `clerkMiddleware` still authenticates the request and `auth()` reflects the real authentication state of the caller. Auth checks performed inside your route handlers, server components, or server actions continue to work correctly and are not affected. Whether your app is affected…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vqx2-fgx2-5wq9</guid>
    </item>
  </channel>
</rss>
