CVE-2026-73418

NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers

State
Published
Severity
7.5 High
Published
Aug 12, 2026
Updated
Aug 13, 2026
Reserved
Aug 12, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HGitHub_M

Weaknesses

Affected Products

ProductVersions
next-authnextauthjs
  • >= 4.0.6, <= 4.24.14Affected
  • >= 5.0.0-beta.0, <= 5.0.0-beta.31Affected
core@auth
  • >= 0.1.0, < 0.41.3Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.