Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
nextauthjs next-auth
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Auth.js是Auth.js组织的一款提供身份验证功能的开发框架。 Auth.js 0.41.3之前版本、next-auth 4.24.15之前版本和next-auth 5.0.0-beta.32之前版本存在安全漏洞，该漏洞源于getToken()函数在处理畸形的Authorization: Bearer头时未正确验证即进行URL解码，导致decodeURIComponent()抛出未捕获异常，可能造成拒绝服务。

CVSS 7.5 · High EPSS 0.88% · P58

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 3

VendorProduct Version RangeStatus
@auth core >= 0.1.0, < 0.41.3 affected
nextauthjs next-auth >= 4.0.6, <= 4.24.14 affected
>= 5.0.0-beta.0, <= 5.0.0-beta.31 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-73418

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
输入验证不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Auth.js 输入验证错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Auth.js是Auth.js组织的一款提供身份验证功能的开发框架。 Auth.js 0.41.3之前版本、next-auth 4.24.15之前版本和next-auth 5.0.0-beta.32之前版本存在安全漏洞，该漏洞源于getToken()函数在处理畸形的Authorization: Bearer头时未正确验证即进行URL解码，导致decodeURIComponent()抛出未捕获异常，可能造成拒绝服务。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
nextauthjs next-auth >= 4.0.6, <= 4.24.14 -
@auth core >= 0.1.0, < 0.41.3 -

II. Public POCs for CVE-2026-73418

# POC Description Source Link Shenlong Link
AI-Generated POC Premium
Qwen3.6-35B-A3B · 10417 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2026-73418

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-73418 (4)

Vendor Advisories for CVE-2026-73418 (1)

Vendor Pages for CVE-2026-73418 (2)

IV. Related Vulnerabilities

Same product: next-auth
Same vendor: nextauthjs
Same weakness: CWE-20

V. Comments for CVE-2026-73418

No comments yet

Leave a comment