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

Published Aug 12, 2026
·
Updated

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.

Affected Software

3 affected components
npm/@auth/core<0.41.3
npm/next-auth<4.24.15
npm/next-auth<5.0.0-beta.32

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade @auth/core to a version that resolves this vulnerability.

    Fixed in 0.41.3
  2. Upgrade

    Upgrade next-auth to a version that resolves this vulnerability.

    Fixed in 4.24.15
  3. Upgrade

    Upgrade next-auth to a version that resolves this vulnerability.

    Fixed in 5.0.0-beta.32

Event History

Aug 12, 2026
CVE Published
via MITRE·08:21 PM
Data Sourced
via MITRE·08:21 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-73418?

CVE-2026-73418 has a high severity rating of 7.5 based on the CVSS score.

2

How do I fix CVE-2026-73418?

To fix CVE-2026-73418, upgrade to @auth/core version 0.41.3 or next-auth versions 4.24.15 and 5.0.0-beta.32 or later.

3

What does CVE-2026-73418 affect?

CVE-2026-73418 affects the getToken() helper in the next-auth/jwt and @auth/core/jwt modules of NextAuth.js.

4

What type of vulnerability is CVE-2026-73418?

CVE-2026-73418 is categorized as an Input Validation vulnerability.

5

What happens when a malformed Bearer authorization header is used with CVE-2026-73418?

Using a malformed Bearer authorization header with CVE-2026-73418 can result in an uncaught exception being thrown.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203
CVE-2026-73418 - NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers - SecAlerts