CyberRota Analysis
AI-GeneratedNextAuth.js versions prior to 0.41.3 for @auth/core and 4.24.15 and 5.0.0-beta.32 for next-auth are vulnerable to a denial of service due to an uncaught exception in the getToken() helper when processing malformed Authorization: Bearer headers. This flaw can be exploited by unauthenticated users to trigger unhandled exceptions in authentication-related code paths, leading to service disruptions without exposing sensitive data. Developers and organizations using affected versions should prioritize upgrading to the patched releases to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
NextAuth.js provides authentication for Next.js. Prior to @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32, the exported getToken() helper in the next-auth/jwt and @auth/core/jwt modules can throw an uncaught exception when it reads a malformed Authorization: Bearer header. When no session cookie is present, getToken() URL-decodes the bearer value before validating it, and malformed percent encoding causes decodeURIComponent() to throw instead of treating the token as invalid. Because getToken() is commonly called in API routes, middleware, and server-side request handlers, a single unauthenticated request can trigger an unhandled exception in code paths that authenticate requests, causing a per-request denial of service without exposing tokens, sessions, or other data and without bypassing authentication. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32.