NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
Summary
| CVE | CVE-2026-73418 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-12 21:17:40 UTC |
| Updated | 2026-08-12 21:17:40 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-20 | CWE-248 | CWE-20 CWE-20: Improper Input Validation | CWE-248 CWE-248: Uncaught Exception
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Nextauthjs | Next-auth | affected >= 4.0.6, <= 4.24.14 | Not specified |
| CNA | Nextauthjs | Next-auth | affected >= 5.0.0-beta.0, <= 5.0.0-beta.31 | Not specified |
| CNA | @auth | Core | affected >= 0.1.0, < 0.41.3 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/nextauthjs/next-auth/releases/tag/next-auth%405.0.0-beta.32 | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059... | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/releases/tag/next-auth%404.24.15 | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/pull/13469 | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/releases/tag/%40auth%2Fcore%400.41.3 | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/security/advisories/GHSA-xmf8-cvqr-rfgj | [email protected] | github.com | |
| github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd1... | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.