p PatchFirst

CVE-2026-73418

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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 · EPSS 0.9% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • next-auth

    Versions
    • >= 4.0.6, <= 4.24.14: Affected
    • >= 5.0.0-beta.0, <= 5.0.0-beta.31: Affected

    No fix published

  • core

    Versions
    • >= 0.1.0, < 0.41.3: Affected

    No fix published

  • @auth/core npm

    Affected ranges
    • SEMVER: ≥ 0.1.0, < 0.41.3

    Update to 0.41.3

  • next-auth npm

    Affected ranges
    • SEMVER: ≥ 5.0.0-beta.0, < 5.0.0-beta.32

    Update to 5.0.0-beta.32

  • next-auth npm

    Affected ranges
    • SEMVER: ≥ 4.0.6, < 4.24.15

    Update to 4.24.15

Original sources

Check your server →