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.5%, top 62% of all CVEs by exploit prediction. 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%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 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_release Patch Available

[email protected]

Patch available: nextauthjs/next-auth [email protected]

https://github.com/nextauthjs/next-auth/releases/tag/next-auth%404.24.15
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 rangeFixed inDependents
@auth/core—0.41.3—
next-auth—5.0.0-beta.32—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 27× 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.

  1. 2026-08-23 11:54 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-22 00:11 UTCEG score recompute
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 00:21 UTCEG score recompute
  6. 2026-08-20 22:56 UTCEPSS rescore
  7. 2026-08-20 00:31 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 00:42 UTCEG score recompute
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 00:52 UTCEG score recompute
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 00:59 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 13:04 UTCEG score recompute
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 13:15 UTCEG score recompute
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 01:31 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 13:36 UTCEG score recompute
  24. 2026-08-13 13:18 UTCEG score recompute
  25. 2026-08-12 21:20 UTCEG score recompute
Show 2 more
  1. 2026-08-12 20:26 UTCEG score recompute
  2. 2026-08-12 20:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 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% probability of exploitation in the next 30 days, which ranks it in the top 61.6% of all scored CVEs.
What is the CVSS score of CVE-2026-73418?
CVE-2026-73418 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-73418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73418, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs