Vulnerability in next (CVE-2026-94484)
Summary
Vulnerability in next (CVE-2026-94484). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 15.5.27 or later.
Original description
The description as published by the source.
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
Source: NIST National Vulnerability Database 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-94484 has been found in next.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade next to 15.5.27 or later.
If unsure, ask your IT team or search "next CVE-2026-94484" on the vendor's site.
CVE-2026-94484 (next) — CWE-524 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 15.5.27 — 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.
A vulnerability (CWE-524) exists in next.
Check the vendor advisory for the affected versions of next.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 15.5.27.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade next to 15.5.27ステージング環境で 15.5.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com