CVE-2026-73418

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (57th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Aug 12, 2026
Patch available. Sources: github_pr, github_commit, github_release.
github_release Patch Available

[email protected]

Patch available: nextauthjs/next-auth [email protected] (pre-release)

https://github.com/nextauthjs/next-auth/releases/tag/next-auth%405.0.0-beta.32
github_commit Patch Available

commit e707770f00c5 (nextauthjs/next-auth)

Patch available: nextauthjs/next-auth @auth/[email protected] (contains commit e707770f00c5)

https://github.com/nextauthjs/next-auth/commit/e707770f00c52b3479e43422b0200b059149ed53
github_commit Patch Available

commit 5bca2399a79b (nextauthjs/next-auth)

Patch available: nextauthjs/next-auth [email protected] (contains commit 5bca2399a79b)

https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05
github_pr Patch Available

fix(next-auth): harden getToken parsing and bind OAuth check cookies to provider

Patch available: nextauthjs/next-auth [email protected] (PR #13469 merged 2026-07-20)

https://github.com/nextauthjs/next-auth/pull/13469

Vendor Advisories for CVE-2026-73418(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@auth/core—
  • 0.1.0 up to 0.41.3: fixed in 0.41.3
—
next-auth—
  • 5.0.0-beta.0 up to 5.0.0-beta.32: fixed in 5.0.0-beta.32
  • 4.0.6 up to 4.24.15: fixed in 4.24.15
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 105 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-07 02:23 UTCEG score recompute
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-06 14:08 UTCEG score recompute
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-05 14:44 UTCEG score recompute
  9. 2026-10-04 23:22 UTCEPSS rescore
  10. 2026-10-03 19:55 UTCEG score recompute
  11. 2026-10-03 14:26 UTCEPSS rescore
  12. 2026-10-02 21:58 UTCEG score recompute
  13. 2026-10-02 08:18 UTCEG score recompute
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-09-30 21:53 UTCEG score recompute
  16. 2026-09-29 15:24 UTCEPSS rescore
  17. 2026-09-29 04:26 UTCEG score recompute
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 01:16 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-27 09:52 UTCEG score recompute
  22. 2026-09-26 15:59 UTCEPSS rescore
  23. 2026-09-25 03:39 UTCEG score recompute
  24. 2026-09-24 00:48 UTCEG score recompute
  25. 2026-09-23 17:54 UTCEPSS rescore
Show 75 more
  1. 2026-09-23 00:27 UTCEG score recompute
  2. 2026-09-22 00:36 UTCEG score recompute
  3. 2026-09-21 21:09 UTCEPSS rescore
  4. 2026-09-21 00:46 UTCEG score recompute
  5. 2026-09-20 20:16 UTCEPSS rescore
  6. 2026-09-20 00:38 UTCEG score recompute
  7. 2026-09-19 00:49 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 00:31 UTCEG score recompute
  10. 2026-09-17 00:16 UTCEG score recompute
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 10:49 UTCEG score recompute
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 09:42 UTCEG score recompute
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-13 21:10 UTCEG score recompute
  17. 2026-09-12 21:21 UTCEG score recompute
  18. 2026-09-12 15:02 UTCEPSS rescore
  19. 2026-09-11 21:30 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:45 UTCEG score recompute
  22. 2026-09-10 09:35 UTCEPSS rescore
  23. 2026-09-09 05:11 UTCEG score recompute
  24. 2026-09-08 22:01 UTCEPSS rescore
  25. 2026-09-07 16:40 UTCEG score recompute
  26. 2026-09-07 01:22 UTCEG score recompute
  27. 2026-09-06 13:48 UTCEPSS rescore
  28. 2026-09-06 01:23 UTCEG score recompute
  29. 2026-09-05 01:25 UTCEG score recompute
  30. 2026-09-04 13:21 UTCEG score recompute
  31. 2026-09-04 05:07 UTCEPSS rescore
  32. 2026-09-02 23:25 UTCEG score recompute
  33. 2026-09-02 14:12 UTCEPSS rescore
  34. 2026-09-01 23:33 UTCEG score recompute
  35. 2026-09-01 13:54 UTCEPSS rescore
  36. 2026-09-01 11:38 UTCEG score recompute
  37. 2026-09-01 04:40 UTCEPSS rescore
  38. 2026-09-01 04:40 UTCEPSS rescore
  39. 2026-08-30 20:23 UTCEG score recompute
  40. 2026-08-30 19:18 UTCEPSS rescore
  41. 2026-08-30 19:17 UTCEPSS rescore
  42. 2026-08-30 08:29 UTCEG score recompute
  43. 2026-08-30 01:22 UTCEPSS rescore
  44. 2026-08-29 08:31 UTCEG score recompute
  45. 2026-08-28 21:42 UTCEPSS rescore
  46. 2026-08-27 23:10 UTCEG score recompute
  47. 2026-08-27 14:25 UTCEPSS rescore
  48. 2026-08-26 23:22 UTCEG score recompute
  49. 2026-08-26 14:47 UTCEPSS rescore
  50. 2026-08-25 23:26 UTCEG score recompute
  51. 2026-08-25 13:49 UTCEPSS rescore
  52. 2026-08-24 23:38 UTCEG score recompute
  53. 2026-08-24 11:44 UTCEG score recompute
  54. 2026-08-23 11:54 UTCEG score recompute
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 00:11 UTCEG score recompute
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-21 00:21 UTCEG score recompute
  59. 2026-08-20 22:56 UTCEPSS rescore
  60. 2026-08-20 00:31 UTCEG score recompute
  61. 2026-08-19 17:04 UTCEPSS rescore
  62. 2026-08-19 00:42 UTCEG score recompute
  63. 2026-08-18 13:49 UTCEPSS rescore
  64. 2026-08-18 13:49 UTCEPSS rescore
  65. 2026-08-18 00:52 UTCEG score recompute
  66. 2026-08-17 13:47 UTCEPSS rescore
  67. 2026-08-17 00:59 UTCEG score recompute
  68. 2026-08-16 14:56 UTCEPSS rescore
  69. 2026-08-16 14:56 UTCEPSS rescore
  70. 2026-08-16 13:04 UTCEG score recompute
  71. 2026-08-16 02:15 UTCEPSS rescore
  72. 2026-08-15 13:15 UTCEG score recompute
  73. 2026-08-15 01:31 UTCEPSS rescore
  74. 2026-08-14 01:31 UTCEG score recompute
  75. 2026-08-13 22:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-73418?
CVE-2026-73418 is a high vulnerability published on August 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…
When was CVE-2026-73418 disclosed?
CVE-2026-73418 was first published on August 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73418 actively exploited?
CVE-2026-73418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73418?
CVE-2026-73418 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73418?
A fix for CVE-2026-73418 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73418 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73418

Explore →

Is Your Infrastructure Affected by CVE-2026-73418?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.