NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
nextauthjs next-auth · @auth core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @auth/core npm |
|
|
| next-auth npm |
|
|
nextauthjs next-auth · @auth core
| Product | Affected | Fixed in |
|---|---|---|
| @auth/core npm |
|
|
| next-auth npm |
|
|
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.
From the CVE record · GitHub_M
The getToken() helper in next-auth/jwt and @auth/core/jwt can throw an uncaught exception when it reads a malformed Authorization: Bearer header and no session cookie is present. An unauthenticated request can cause a per-request denial of service in API routes, middleware, or server-side handlers that call the helper; no user interaction is required.
Check npm installations of @auth/core >=0.1.0 <0.41.3 and next-auth >=4.0.6 <4.24.15 or >=5.0.0-beta.0 <5.0.0-beta.32.