← Back
CVE-2026-73419
medium
CVSS 6.8
Vulnerability in @auth/core (CVE-2026-73419)
Summary
vulnerability in @auth/core (CVE-2026-73419). Confidential information can be exposed externally. Exploitable via ``state``. Mitigation: upgrade to `0.41.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-73419** has been found in @auth/core.
Attackers can target a specific entry point like ``state`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade @auth/core to **0.41.3** or later.
If unsure, ask your IT team or search "@auth/core CVE-2026-73419" on the vendor's site.
CVE-2026-73419 (@auth/core) — CWE-345 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `state` / `nonce` / `events.linkAccount`
Patched: `0.41.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-345) exists in @auth/core. Attackers reach the vulnerable code path via ``state`` without authentication.
📍 Affected scope
@auth/core — . Attack surface: `state` / `nonce` / `events.linkAccount`.
🔥 Severity
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.41.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@auth/core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@auth/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@auth/core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @auth/core to 0.41.3ステージング環境で 0.41.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@auth/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.41.3"}]}]
npm
next-auth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.24.15"}]}]
References
- web https://github.com/nextauthjs/next-auth/security/advisories/GHSA-x445-f3h2-j279
- web https://github.com/nextauthjs/next-auth/pull/13469
- web https://github.com/nextauthjs/next-auth/commit/5bca2399a79ba8d116ca5179b4b1ebcd152e7f05
- web https://github.com/nextauthjs/next-auth/commit/9f7a97fade9b1319bb9ac19fc9828d62e0a2a852
- web https://github.com/nextauthjs/next-auth/releases/tag/@auth/[email protected]
- web https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- web https://github.com/nextauthjs/next-auth/releases/tag/[email protected]
- web https://github.com/advisories/GHSA-x445-f3h2-j279
- web https://nvd.nist.gov/vuln/detail/CVE-2026-73419