CVE-2026-73419: nextauthjs next-auth · Insufficient Verification of Data Authenticity
Affects nextauthjs next-authSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 5.0.0-beta.32 or 4.24.15 when convenient.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.0-beta.32, 4.24.15, 0.41.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade next-auth to 5.0.0-beta.32 or 4.24.15; core to 0.41.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nextauthjsnext-auth | Affected
| Fixed in
|
| nextauthjsnext-auth | Affected
| Fixed in
|
| @authcore | Affected
| Fixed in
|
AI-suggested
A fix is available in @auth/core version 0.41.3 and next-auth versions 4.24.15 and 5.0.0-beta.32. Users of affected versions should upgrade to these or later versions to remediate the vulnerability. No alternative mitigations are indicated in the advisory.
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, 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.
References
- github.com/nextauthjs/next-auth/security/advisories/GHSA-x445-f3h2-j279 (opens in a new tab)
- github.com/nextauthjs/next-auth/pull/13469 (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05 (opens in a new tab)
- github.com/nextauthjs/next-auth/commit/9f7a97fade9b1319bb9ac19fc9828d62e0a2a852 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/@auth/core@0.41.3 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth@4.24.15 (opens in a new tab)
- github.com/nextauthjs/next-auth/releases/tag/next-auth@5.0.0-beta.32 (opens in a new tab)