<?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>Sat, 03 Oct 2026 04:08:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233953</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233953</link>
      <description>EUVD-2026-233953</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233953</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31093</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31093</link>
      <description>&lt;p&gt;NextAuth.js is a complete open source authentication solution for Next.js applications. In affected versions an attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally is converted to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to the **API route handler timing out and logging in to fail**. This has been remedied in versions 3.29.5 and 4.5.0. If for some reason you cannot upgrade, the workaround requires you to rely on Advanced Initialization. Please see the documentation for more.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NextAuth.js is a complete open source authentication solution for Next.js applications. In affected versions an attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally is converted to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to the **API route handler timing out and logging in to fail**. This has been remedied in versions 3.29.5 and 4.5.0. If for some reason you cannot upgrade, the workaround requires you to rely on Advanced Initialization. Please see the documentation for more.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31093</guid>
    </item>
    <item>
      <title>GHSA-g5fm-jp9v-2432 — Improper Handling of `callbackUrl` parameter in next-auth</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g5fm-jp9v-2432</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: next-auth&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally we convert to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to our **API route handler timing out and logging in to fail**. This has been remedied in the following releases:&lt;/p&gt;
&lt;p&gt;next-auth v3 users before version 3.29.5 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. See our [migration guide](https://next-auth.js.org/getting-started/upgrade-v4))&lt;/p&gt;
&lt;p&gt;next-auth v4 users before version 4.5.0 are impacted.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve released patches for this vulnerability in:
  
- v3 - `3.29.5`
- v4 - `4.5.0`&lt;/p&gt;
&lt;p&gt;You can do:&lt;/p&gt;
&lt;p&gt;```sh
npm i next-auth@latest
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```sh
yarn add next-auth@latest
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```sh
pnpm add next-auth@latest
```&lt;/p&gt;
&lt;p&gt;(This will update to the latest v4 version, but you can change  `latest` to `3` if you want to stay on v3. This is not recommended.)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If for some reason you cannot upgrade, the workaround requires you to rely on [Advanced Initialization](https://next-auth.js.org/configuration/initialization#advanced-initialization). Here is an example:&lt;/p&gt;
&lt;p&gt;**Before:**&lt;/p&gt;
&lt;p&gt;```js
// pages/api/auth/[...nextauth].js
import NextAuth from &amp;#34;next-auth&amp;#34;&lt;/p&gt;
&lt;p&gt;export default NextAuth(/* your config */)
```&lt;/p&gt;
&lt;p&gt;**After:**&lt;/p&gt;
&lt;p&gt;```js
// pages/api/auth/[...nextauth].js
import NextAuth from &amp;#34;next-auth&amp;#34;&lt;/p&gt;
&lt;p&gt;function isValidH…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: next-auth&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can send a request to an app using NextAuth.js with an invalid `callbackUrl` query parameter, which internally we convert to a `URL` object. The URL instantiation would fail due to a malformed URL being passed into the constructor, causing it to throw an unhandled error which led to our **API route handler timing out and logging in to fail**. This has been remedied in the following releases:&lt;/p&gt;
&lt;p&gt;next-auth v3 users before version 3.29.5 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. See our [migration guide](https://next-auth.js.org/getting-started/upgrade-v4))&lt;/p&gt;
&lt;p&gt;next-auth v4 users before version 4.5.0 are impacted.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve released patches for this vulnerability in:
  
- v3 - `3.29.5`
- v4 - `4.5.0`&lt;/p&gt;
&lt;p&gt;You can do:&lt;/p&gt;
&lt;p&gt;```sh
npm i next-auth@latest
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```sh
yarn add next-auth@latest
```&lt;/p&gt;
&lt;p&gt;or&lt;/p&gt;
&lt;p&gt;```sh
pnpm add next-auth@latest
```&lt;/p&gt;
&lt;p&gt;(This will update to the latest v4 version, but you can change  `latest` to `3` if you want to stay on v3. This is not recommended.)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If for some reason you cannot upgrade, the workaround requires you to rely on [Advanced Initialization](https://next-auth.js.org/configuration/initialization#advanced-initialization). Here is an example:&lt;/p&gt;
&lt;p&gt;**Before:**&lt;/p&gt;
&lt;p&gt;```js
// pages/api/auth/[...nextauth].js
import NextAuth from &amp;#34;next-auth&amp;#34;&lt;/p&gt;
&lt;p&gt;export default NextAuth(/* your config */)
```&lt;/p&gt;
&lt;p&gt;**After:**&lt;/p&gt;
&lt;p&gt;```js
// pages/api/auth/[...nextauth].js
import NextAuth from &amp;#34;next-auth&amp;#34;&lt;/p&gt;
&lt;p&gt;function isValidH…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g5fm-jp9v-2432</guid>
    </item>
    <item>
      <title>gsd-2022-31093</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31093</link>
      <description>gsd-2022-31093</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31093</guid>
    </item>
  </channel>
</rss>
