@auth/core
Affected
- introduced
0.1.0, fixed0.41.3(semver)
Fixed versions
0.41.3
Fix
- Fixed version
0.41.3npm install @auth/[email protected]
Advisory
Also known as: 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. 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:
next-auth <= 5.0.0-beta.25 (or @auth/core exposing the same getToken() implementation).getToken() directly — for example in a Route Handler, middleware, or server-side request handler.getToken() call in your own try/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
getToken().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:
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
}
Authorization header at the edge (proxy, middleware) before it reaches getToken(), rejecting values whose Bearer portion is not valid percent-encoding.Credit
Reported by @deprrous. Thank you for the responsible disclosure.
High Basis: The source's own band: HIGH
0.1.0, fixed 0.41.3 (semver)0.41.3
0.41.3npm install @auth/[email protected]5.0.0-beta.0, fixed 5.0.0-beta.32 (semver)5.0.0-beta.32
5.0.0-beta.32npm install [email protected]4.0.6, fixed 4.24.15 (semver)4.24.15
4.24.15npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0