Threat Intelligence Database

NextAuth.js versions from 5.0.0-beta.0 up to but not including 5.0.0-beta.32 have an improper authorization vulnerability. When the server configuration is invalid, such as missing issuer and authorization endpoint or unset AUTH_SECRET, the auth() wrapper returns a truthy error object instead of null for unauthenticated requests. This causes checks that rely solely on the existence of the auth object to incorrectly grant access to all visitors. The issue is fixed in next-auth 5.0.0-beta.32.

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.