← Back
CVE-2026-64646
medium
CVSS 5.3
Vulnerability in next (CVE-2026-64646)
Summary
vulnerability in next (CVE-2026-64646). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `16.2.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-64646** has been found in next.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade next to **16.2.11** or later.
If unsure, ask your IT team or search "next CVE-2026-64646" on the vendor's site.
CVE-2026-64646 (next) — CWE-770 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `16.2.11` — apply immediately
Workaround: If you cannot upgrade, ensure your hosting provider limits the request's body size.
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-770) exists in next.
📍 Affected scope
next — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **16.2.11**.
🛡️ Workaround
Workaround: If you cannot upgrade, ensure your hosting provider limits the request's body size.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If you cannot upgrade, ensure your hosting provider limits the request's body size.パッチが適用されるまでの応急処置として、If you cannot upgrade, ensure your hosting provider limits the request's body size. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade next to 16.2.11ステージング環境で 16.2.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
next
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.2.11"}]}]
References
- patch [email protected]
- patch [email protected]
- patch [email protected]
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-4c39-4ccg-62r3