CVE-2026-73418 NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
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.
Upgrade path
4 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| @auth core(npm) | >= 0.1.0, < 0.41.3 | 0.41.3 | Fixed |
| npm next-auth(npm) | >= 4.0.6, < 4.24.15; >= 4.0.6, <= 4.24.14; >= 5.0.0-beta.0, < 5.0.0-beta.32; >= 5.0.0-beta.0, <= 5.0.0-beta.31 | 4.24.15, 5.0.0-beta.32 | Fixed |
| @auth core | = >= 0.1.0, < 0.41.3 | No fix listed | Versions listed |
| nextauthjs next-auth | = >= 4.0.6, <= 4.24.14; = >= 5.0.0-beta.0, <= 5.0.0-beta.31 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| nextauthjs next-auth | = >= 4.0.6, <= 4.24.14 | No fix listed |
| nextauthjs next-auth | = >= 5.0.0-beta.0, <= 5.0.0-beta.31 | No fix listed |
| @auth core | = >= 0.1.0, < 0.41.3 | No fix listed |
| @auth core(npm) | >= 0.1.0, < 0.41.3 | 0.41.3 |
| npm next-auth(npm) | >= 5.0.0-beta.0, <= 5.0.0-beta.31 | No fix listed |
| npm next-auth(npm) | >= 4.0.6, <= 4.24.14 | No fix listed |
| npm next-auth(npm) | >= 5.0.0-beta.0, < 5.0.0-beta.32 | 5.0.0-beta.32 |
| npm next-auth(npm) | >= 4.0.6, < 4.24.15 | 4.24.15 |
References
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xmf8-cvqr-rfgj vendor-advisory
- https://github.com/nextauthjs/next-auth/pull/13469 patch
- https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05 patch
- https://github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059149ed53 patch
- https://github.com/nextauthjs/next-auth/releases/tag/%40auth%2Fcore%400.41.3
- https://github.com/nextauthjs/next-auth/releases/tag/next-auth%404.24.15
- https://github.com/nextauthjs/next-auth/releases/tag/next-auth%405.0.0-beta.32
- github.com patch
- github.com
- github.com
- github.com
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product
- ENISA EUVD EUVD-2026-57552 third-party-advisory