<?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 09:19:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-247129</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-247129</link>
      <description>EUVD-2026-247129</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-247129</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53548</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53548</link>
      <description>&lt;p&gt;Clerk helps developers build user management. Applications that use the verifyWebhook() helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events. The issue was resolved in @clerk/backend 2.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Clerk helps developers build user management. Applications that use the verifyWebhook() helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events. The issue was resolved in @clerk/backend 2.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53548</guid>
    </item>
    <item>
      <title>GHSA-9mp4-77wg-rwx9 — @clerk/backend Performs Insufficient Verification of Data Authenticity</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9mp4-77wg-rwx9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @clerk/backend, npm: @clerk/astro, npm: @clerk/express, npm: @clerk/fastify, npm: @clerk/nextjs, npm: @clerk/nuxt, npm: @clerk/react-router, npm: @clerk/remix, npm: @clerk/tanstack-react-start&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Applications that use the `verifyWebhook()` helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* `@clerk/backend`: the helper has been patched as of `2.4.0`
* `@clerk/astro`: the helper has been patched as of `2.10.2`
* `@clerk/express`: the helper has been patched as of `1.7.4`
* `@clerk/fastify`: the helper has been patched as of `2.4.4`
* `@clerk/nextjs`: the helper has been patched as of `6.23.3`
* `@clerk/nuxt`: the helper has been patched as of `1.7.5`
* `@clerk/react-router`: the helper has been patched as of `1.6.4`
* `@clerk/remix`: the helper has been patched as of `4.8.5`
* `@clerk/tanstack-react-start`: the helper has been patched as of `0.18.3`&lt;/p&gt;
&lt;p&gt;### Resolution&lt;/p&gt;
&lt;p&gt;The issue was resolved in **`@clerk/backend` `2.4.0`** by:&lt;/p&gt;
&lt;p&gt;* Properly parsing the webhook request&amp;#39;s signatures and comparing them against the signature generated from the received event&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If unable to upgrade, developers can workaround this issue by verifying webhooks manually, per [this documentation](https://clerk.com/docs/webhooks/overview#protect-your-webhooks-from-abuse).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @clerk/backend, npm: @clerk/astro, npm: @clerk/express, npm: @clerk/fastify, npm: @clerk/nextjs, npm: @clerk/nuxt, npm: @clerk/react-router, npm: @clerk/remix, npm: @clerk/tanstack-react-start&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Applications that use the `verifyWebhook()` helper to verify incoming Clerk webhooks are susceptible to accepting improperly signed webhook events.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* `@clerk/backend`: the helper has been patched as of `2.4.0`
* `@clerk/astro`: the helper has been patched as of `2.10.2`
* `@clerk/express`: the helper has been patched as of `1.7.4`
* `@clerk/fastify`: the helper has been patched as of `2.4.4`
* `@clerk/nextjs`: the helper has been patched as of `6.23.3`
* `@clerk/nuxt`: the helper has been patched as of `1.7.5`
* `@clerk/react-router`: the helper has been patched as of `1.6.4`
* `@clerk/remix`: the helper has been patched as of `4.8.5`
* `@clerk/tanstack-react-start`: the helper has been patched as of `0.18.3`&lt;/p&gt;
&lt;p&gt;### Resolution&lt;/p&gt;
&lt;p&gt;The issue was resolved in **`@clerk/backend` `2.4.0`** by:&lt;/p&gt;
&lt;p&gt;* Properly parsing the webhook request&amp;#39;s signatures and comparing them against the signature generated from the received event&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If unable to upgrade, developers can workaround this issue by verifying webhooks manually, per [this documentation](https://clerk.com/docs/webhooks/overview#protect-your-webhooks-from-abuse).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9mp4-77wg-rwx9</guid>
    </item>
  </channel>
</rss>
