NextAuth.js: OAuth state, nonce, and PKCE check cookies are not bound to the provider that created them
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-345.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| nextauthjs | next-auth | before 4.24.15; 5.0.0-beta.4 to before 5.0.0-beta.32 | 4.24.15, 5.0.0-beta.32 | Patch available | CNA |
| @auth | core | before 0.41.3 | 0.41.3 | Patch available | CNA |
| — | @auth/core (npm) | before 0.41.3 | 0.41.3 | Patch available | GHSA-x445-f3h2-j279 |
| — | next-auth (npm) | 5.0.0-beta.1 to before 5.0.0-beta.32 | 5.0.0-beta.32 | Patch available | GHSA-x445-f3h2-j279 |
| — | next-auth (npm) | before 4.24.15 | 4.24.15 | Patch available | GHSA-x445-f3h2-j279 |
- next-auth Vendornextauthjs Affected before 4.24.15; 5.0.0-beta.4 to before 5.0.0-beta.32 Fixed in 4.24.15, 5.0.0-beta.32 Patch available CNA
- core Vendor@auth Affected before 0.41.3 Fixed in 0.41.3 Patch available CNA
- @auth/core (npm) Vendor— Affected before 0.41.3 Fixed in 0.41.3 Patch available GHSA-x445-f3h2-j279
- next-auth (npm) Vendor— Affected 5.0.0-beta.1 to before 5.0.0-beta.32 Fixed in 5.0.0-beta.32 Patch available GHSA-x445-f3h2-j279
- next-auth (npm) Vendor— Affected before 4.24.15 Fixed in 4.24.15 Patch available GHSA-x445-f3h2-j279
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:*:*:* | — | — | nextauthjs |
- cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:*:*:* Versions — — ·nextauthjs
Remediation
- Fix · CNA next-auth (nextauthjs) Fixed in 4.24.15, 5.0.0-beta.32
- Fix · CNA core (@auth) Fixed in 0.41.3
- Fix · GHSA-x445-f3h2-j279 @auth/core (npm) Fixed in 0.41.3 Advisory →
- Fix · GHSA-x445-f3h2-j279 next-auth (npm) Fixed in 5.0.0-beta.32 Advisory →
- Fix · GHSA-x445-f3h2-j279 next-auth (npm) Fixed in 4.24.15 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-73419
- 2026-10-03 Alias added: GHSA-x445-f3h2-j279
References
Other 8
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-x445-f3h2-j279
- https://github.com/nextauthjs/next-auth/pull/13469
- https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05
- https://github.com/nextauthjs/next-auth/commit/9f7a97fade9b1319bb9ac19fc9828d62e0a2a852
- https://github.com/nextauthjs/next-auth/releases/tag/@auth/[email protected]
- https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- https://github.com/nextauthjs/next-auth
More nextauthjs vulnerabilities
- TI-2022-13171 Improper handling of email input in next-auth CVSS 3.1HIGH 7.1
- TI-2022-16351 Verification requests (magic link) sent to unwanted emails CVSS 3.1CRITICAL 9.1
- TI-2026-51538 NextAuth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass CVSS 4.0CRITICAL 9.1
- TI-2026-51539 Improper authorization in nextauthjs next-auth CVSS 4.0CRITICAL 9.1
- TI-2022-13137 Improper Handling of `callbackUrl` parameter in next-auth CVSS 3.1HIGH 7.5
- TI-2023-12218 Missing proper state, nonce and PKCE checks for OAuth authentication in next-auth CVSS 3.1HIGH 8.8
Sources
- CVE-2026-73419 · CVE Program
- CVE-2026-73419 · NVD
- FIRST EPSS
- GHSA-x445-f3h2-j279 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences