← Back
CVE-2026-44573
high
CVSS 7.5
Authorization Flaw in next (CVE-2026-44573)
Summary
vulnerability in next (CVE-2026-44573). Confidential information can be exposed externally. Exploitable via ``i18n``. Mitigation: upgrade to `16.2.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44573** has been found in next.
Attackers can target a specific entry point like ``i18n`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade next to **16.2.5** or later.
If unsure, ask your IT team or search "next CVE-2026-44573" on the vendor's site.
CVE-2026-44573 (next) — CWE-863 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `i18n`
Patched: `16.2.5` — 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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in next. Attackers reach the vulnerable code path via ``i18n`` without authentication.
📍 Affected scope
next — . Attack surface: `i18n`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **16.2.5**.
🛡️ Workaround
Workaround: If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.
🔍 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 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. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade next to 16.2.5ステージング環境で 16.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
next
[{"type":"SEMVER","events":[{"introduced":"16.0.0"},{"fixed":"16.2.5"}]}]