Vulnerability in next (CVE-2026-64642)
Summary
Vulnerability in next (CVE-2026-64642). Confidential information can be exposed externally. Exploitable via config.i18n.locales. Mitigation: upgrade to 16.2.11 or later.
Original description
The description as published by the source.
Impact
Crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication.
Workarounds
If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-64642 has been found in next.
Attackers can target a specific entry point like config.i18n.locales over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade next to 16.2.11 or later.
If unsure, ask your IT team or search "next CVE-2026-64642" on the vendor's site.
CVE-2026-64642 (next) — CWE-285 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: config.i18n.locales
Patched: 16.2.11 — apply immediately
Workaround: If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.
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.
A vulnerability (CWE-285) exists in next. Attackers reach the vulnerable code path via config.i18n.locales without authentication.
Check the vendor advisory for the affected versions of next. Attack surface: config.i18n.locales.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 16.2.11.
Workaround: If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'next' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'next' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nextを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade next to 16.2.11ステージング環境で 16.2.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。