Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44578 high CVSS 8.6

SSRF (Server-Side Request Forgery) in next (CVE-2026-44578)

Summary

SSRF in next (CVE-2026-44578). Confidential information can be exposed externally. Mitigation: upgrade to 16.2.5 or later.

Original description

The description as published by the source.

Next.js is a React framework for building full-stack web applications. From 13.4.13 to before 15.5.16 and 16.2.5, self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected. This vulnerability is fixed in 15.5.16 and 16.2.5.

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-44578 has been found in next.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade next to 16.2.5 or later.
If unsure, ask your IT team or search "next CVE-2026-44578" on the vendor's site.

CVE-2026-44578 (next) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 16.2.5 — apply immediately
Workaround: If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks.
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

SSRF (CWE-918) exists in next.

📍 Affected scope

Check the vendor advisory for the affected versions of next.

🔥 Severity

Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 16.2.5.

🛡️ Workaround

Workaround: If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks.

🔍 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'next' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で next を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks.

    パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade next to 16.2.5

    ステージング環境で 16.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm next
[{"type":"SEMVER","events":[{"introduced":"16.0.0"},{"fixed":"16.2.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details