CVE-2026-73419

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (14th 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
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.8Exploit: 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, Auth.js stores the OAuth/OIDC anti-CSRF checks state, nonce, and the PKCE verifier in global cookies that are not bound to the provider that created them. On callback, a check value minted during a sign-in started with one provider can satisfy the callback for a different provider because the stored cookie is not verified against the callback provider's identity, including the provider ID, issuer, client ID, or redirect URI. In a multi-provider application that permits account linking while logged in, when one provider's authorization request is observable and a target provider callback can be satisfied without a PKCE verifier, an attacker can lure a victim into starting a legitimate same-origin flow and link the attacker's target-provider account to the victim's Auth.js user. The linked provider grants the attacker persistent sign-in to the victim's account, while cross-site request forgery alone is insufficient. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 (6)

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

[email protected]

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

https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
github_release Patch Available

[email protected]

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

https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
github_commit Patch Available

commit 9f7a97fade9b (nextauthjs/next-auth)

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

https://github.com/nextauthjs/next-auth/commit/9f7a97fade9b1319bb9ac19fc9828d62e0a2a852
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
githubMentions a patch (unverified)

OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them · Advisory · nextauthjs/next-auth · GitHub

https://github.com/nextauthjs/next-auth/security/advisories/GHSA-x445-f3h2-j279

Vendor Advisories for CVE-2026-73419(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—
  • every version up to 0.41.3: fixed in 0.41.3
—
next-auth—
  • 5.0.0-beta.1 up to 5.0.0-beta.32: fixed in 5.0.0-beta.32
  • every version up to 4.24.15: fixed in 4.24.15
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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-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-06 15:18 UTCEPSS rescore
  5. 2026-10-06 14:08 UTCEG score recompute
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 19:55 UTCEG score recompute
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-02 08:17 UTCEG score recompute
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 21:53 UTCEG score recompute
  13. 2026-09-29 15:24 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 12:27 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-27 09:52 UTCEG score recompute
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 04:45 UTCEG score recompute
  20. 2026-09-24 02:58 UTCEG score recompute
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-23 01:10 UTCEG score recompute
  23. 2026-09-21 23:22 UTCEG score recompute
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-20 21:35 UTCEG score recompute
Show 66 more
  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 19:43 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 16:56 UTCEG score recompute
  5. 2026-09-17 13:44 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 10:49 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 08:04 UTCEG score recompute
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 06:17 UTCEG score recompute
  12. 2026-09-13 04:31 UTCEG score recompute
  13. 2026-09-12 15:02 UTCEPSS rescore
  14. 2026-09-12 02:44 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 00:57 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 05:11 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:40 UTCEG score recompute
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-06 04:59 UTCEG score recompute
  23. 2026-09-05 03:13 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-02 23:25 UTCEG score recompute
  26. 2026-09-02 14:12 UTCEPSS rescore
  27. 2026-09-01 15:15 UTCEG score recompute
  28. 2026-09-01 13:54 UTCEPSS rescore
  29. 2026-08-31 12:18 UTCEG score recompute
  30. 2026-08-30 19:18 UTCEPSS rescore
  31. 2026-08-30 19:17 UTCEPSS rescore
  32. 2026-08-30 10:23 UTCEG score recompute
  33. 2026-08-30 01:22 UTCEPSS rescore
  34. 2026-08-29 08:31 UTCEG score recompute
  35. 2026-08-28 21:42 UTCEPSS rescore
  36. 2026-08-27 16:29 UTCEG score recompute
  37. 2026-08-27 14:25 UTCEPSS rescore
  38. 2026-08-26 14:47 UTCEPSS rescore
  39. 2026-08-26 13:54 UTCEG score recompute
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-25 12:08 UTCEG score recompute
  42. 2026-08-24 10:22 UTCEG score recompute
  43. 2026-08-22 06:49 UTCEG score recompute
  44. 2026-08-21 23:49 UTCEPSS rescore
  45. 2026-08-21 05:02 UTCEG score recompute
  46. 2026-08-20 22:56 UTCEPSS rescore
  47. 2026-08-20 03:15 UTCEG score recompute
  48. 2026-08-19 17:04 UTCEPSS rescore
  49. 2026-08-19 01:23 UTCEG score recompute
  50. 2026-08-18 13:49 UTCEPSS rescore
  51. 2026-08-18 13:49 UTCEPSS rescore
  52. 2026-08-17 23:37 UTCEG score recompute
  53. 2026-08-17 13:47 UTCEPSS rescore
  54. 2026-08-16 21:50 UTCEG score recompute
  55. 2026-08-16 14:56 UTCEPSS rescore
  56. 2026-08-16 14:56 UTCEPSS rescore
  57. 2026-08-16 02:15 UTCEPSS rescore
  58. 2026-08-15 20:04 UTCEG score recompute
  59. 2026-08-15 01:31 UTCEPSS rescore
  60. 2026-08-14 18:17 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-13 16:30 UTCEG score recompute
  63. 2026-08-13 16:02 UTCEG score recompute
  64. 2026-08-12 21:20 UTCEG score recompute
  65. 2026-08-12 20:41 UTCEG score recompute
  66. 2026-08-12 20:40 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73419?
CVE-2026-73419 is a medium 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, Auth.js stores the OAuth/OIDC anti-CSRF checks state, nonce, and the PKCE verifier in global cookies that are not bound to the provider that created them. On callback, a check value…
When was CVE-2026-73419 disclosed?
CVE-2026-73419 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-73419 actively exploited?
CVE-2026-73419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73419?
CVE-2026-73419 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73419?
A fix for CVE-2026-73419 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73419 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-73419

Explore →

Is Your Infrastructure Affected by CVE-2026-73419?

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

Book a Demo →Browse All CVEs