CVE-2026-73418: nextauthjs next-auth · Improper Input Validation
Affects nextauthjs next-authSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 4.24.15 soon.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.41.3, 4.24.15
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade next-auth to 4.24.15; core and @auth/core to 0.41.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nextauthjsnext-auth | Affected
| Fixed in– |
| @authcore | Affected
| Fixed in
|
npm@auth/corepkg:npm/@auth/coreOther threats | Affected
| Fixed in
|
npmnext-authpkg:npm/next-authOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in @auth/core version 0.41.3, next-auth version 4.24.15, and 5.0.0-beta.32. Users should upgrade to these or later versions to remediate the issue. No other mitigation is required as the vulnerability is addressed by the official fix.
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.
References
- github.com/nextauthjs/next-auth/security/advisories/GHSA-xmf8-cvqr-rfgj (opens in a new tab)
- github.com/nextauthjs/next-auth/pull/13469 (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05 (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059149ed53 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/%40auth%2Fcore%400.41.3 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth%404.24.15 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth%405.0.0-beta.32 (opens in a new tab)