Answer in brief
CVE-2026-73418 records a High severity (CVSS 7.5) vulnerability in NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers. The current sources do not mark it as known exploited. The current feed maps @auth/core (generic), nextauthjs/next-auth (generic), @auth/core (npm), @auth/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-73418 records a High severity (CVSS 7.5) vulnerability in NextAuth.js: getToken() throws an uncaught exception on malformed Bearer authorization headers. The current sources do not mark it as known exploited. The current feed maps @auth/core (generic), nextauthjs/next-auth (generic), @auth/core (npm), @auth/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @auth/core (generic), nextauthjs/next-auth (generic), @auth/core (npm), @auth/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @auth/coregeneric | >= 0.1.0, < 0.41.3 | Not reported |
| nextauthjs/next-authgeneric | >= 4.0.6, <= 4.24.14 || >= 5.0.0-beta.0, <= 5.0.0-beta.31 | Not reported |
| @auth/corenpm | >=0.1.0 <0.41.3 | 0.41.3 |
| @auth/corenpm | >=0.1.0,<0.41.3 | 0.41.3 |
| next-authnpm | >=5.0.0-beta.0 <5.0.0-beta.32 | 5.0.0-beta.32 |
| next-authnpm | >=4.0.6 <4.24.15 | 4.24.15 |
| next-authnpm | >=5.0.0-beta.0,<=5.0.0-beta.31 | 5.0.0-beta.32 |
| next-authnpm | >=4.0.6,<=4.24.14 | 4.24.15 |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @auth/core (generic), nextauthjs/next-auth (generic), @auth/core (npm), @auth/core (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @auth/coregeneric | >= 0.1.0, < 0.41.3 | Not reported |
| nextauthjs/next-authgeneric | >= 4.0.6, <= 4.24.14 || >= 5.0.0-beta.0, <= 5.0.0-beta.31 | Not reported |
| @auth/corenpm | >=0.1.0 <0.41.3 | 0.41.3 |
| @auth/corenpm | >=0.1.0,<0.41.3 | 0.41.3 |
| next-authnpm | >=5.0.0-beta.0 <5.0.0-beta.32 | 5.0.0-beta.32 |
| next-authnpm | >=4.0.6 <4.24.15 | 4.24.15 |
| next-authnpm | >=5.0.0-beta.0,<=5.0.0-beta.31 | 5.0.0-beta.32 |
| next-authnpm | >=4.0.6,<=4.24.14 | 4.24.15 |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.