CVE-2026-73418: Auth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
Summary The exported getToken() helper (next-auth/jwt and @auth/core/jwt) 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 the decode step to throw rather than being treated as an invalid token.
Published Jul 23, 2026 · Updated Aug 13, 2026
Affected packages
@auth/core
- Ecosystem
- npm
- Affected
- >= 0.1.0, < 0.41.3
- Fixed in
- 0.41.3
- Check
npm ls @auth/core
next-auth
- Ecosystem
- npm
- Affected
- >= 5.0.0-beta.0, <= 5.0.0-beta.31
- Fixed in
- 5.0.0-beta.32
- Check
npm ls next-auth
next-auth
- Ecosystem
- npm
- Affected
- >= 4.0.6, <= 4.24.14
- Fixed in
- 4.24.15
- Check
npm ls next-auth
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The exported getToken() helper (next-auth/jwt and @auth/core/jwt) 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 the decode step to throw rather than being treated as an invalid token. Because getToken() is commonly called in API routes, middleware, and other request handlers, a single unauthenticated request can trigger an unhandled exception in code paths that authenticate requests.
Am I affected?
You are affected if all of the following hold:
- You use
next-auth<= 5.0.0-beta.25(or@auth/coreexposing the samegetToken()implementation). - Your application calls
getToken()directly — for example in a Route Handler, middleware, or server-side request handler. - You do not wrap that
getToken()call in your owntry/catch.
You are not affected if you only use the framework's auth() helper and never call getToken() yourself, or if every getToken() call site already has its own exception handling.
Impact
- Denial of service: an unauthenticated request carrying a malformed Bearer authorization header can raise an unhandled exception in any handler that calls
getToken(). - The impact is per-request and limited to availability; it does not expose tokens, sessions, or other data, and does not bypass authentication.
CWE-20: Improper Input Validation.
Patched version
The fix makes getToken() treat a malformed Bearer value as an invalid token and return null, matching how other undecodable tokens are already handled. Upgrade to the first release containing this fix (to be published; this advisory will be updated with the exact patched version before publication) and no code changes are required.
Workarounds
If you cannot upgrade immediately, either:
- Config/code-level: wrap your
getToken()calls so a thrown error is treated as "no token", e.g.
let token = null
try {
token = await getToken({ req, secret })
} catch {
token = null
}- Or strip/normalize the incoming
Authorizationheader at the edge (proxy, middleware) before it reachesgetToken(), rejecting values whose Bearer portion is not valid percent-encoding.
Credit
Reported by @deprrous. Thank you for the responsible disclosure.
Credited to deprrous.
References
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xmf8-cvqr-rfgj
- https://github.com/nextauthjs/next-auth/pull/13467
- https://github.com/nextauthjs/next-auth/pull/13469
- https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05
- https://github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059149ed53
- https://github.com/nextauthjs/next-auth/releases/tag/@auth/[email protected]
- https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- https://nvd.nist.gov/vuln/detail/CVE-2026-73418
- https://github.com/advisories/GHSA-xmf8-cvqr-rfgj
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-73419
Auth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them
medium6.8Jul 23, 2026CVE-2026-73420
Auth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass
critical9.1Jul 23, 2026CVE-2026-73421
Auth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error)
critical9.1Jul 23, 2026GHSA-5jpx-9hw9-2fx4
NextAuthjs Email misdelivery Vulnerability
medium6.9Oct 29, 2025
