CVE-2026-73418NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
Updated under an hour ago ()
Does this affect you?
It affects nextauthjs next-auth and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-20, CWE-248
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Awaiting Analysis
- Record last updated
- Aug 13, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
nextauthjs next-auth nextauthjs:next_auth (from the name) | from 4.0.6, <= 4.24.14; from 5.0.0-beta.0, <= 5.0.0-beta.31 | CNA record |
@auth core auth:core (from the name) | from 0.1.0, < 0.41.3 | CNA record |
References
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xmf8-cvqr-rfgjx-refsource-confirm
- https://github.com/nextauthjs/next-auth/pull/13469x-refsource-misc
- https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05x-refsource-misc
- https://github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059149ed53x-refsource-misc
- https://github.com/nextauthjs/next-auth/releases/tag/%40auth%2Fcore%400.41.3x-refsource-misc
- https://github.com/nextauthjs/next-auth/releases/tag/next-auth%404.24.15x-refsource-misc
- https://github.com/nextauthjs/next-auth/releases/tag/next-auth%405.0.0-beta.32x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.