Vulnerability in next (CVE-2022-36046)
Summary
Vulnerability in next (CVE-2022-36046). Risk of unauthorized operations or information disclosure. Exploitable via unhandledRejection. Mitigation: upgrade to 12.2.4 or later.
Original description
The description as published by the source.
Impact
When specific requests are made to the Next.js server it can cause an unhandledRejection in the server which can crash the process to exit in specific Node.js versions with strict unhandledRejection handling.
-
Affected: All of the following must be true to be affected by this CVE
- Node.js version above v15.0.0 being used with strict
unhandledRejectionexiting - Next.js version v12.2.3
- Using next start or a custom server
- Node.js version above v15.0.0 being used with strict
-
Not affected: Deployments on Vercel (vercel.com) are not affected along with similar environments where
next-serverisn't being shared across requests.
Patches
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2022-36046 has been found in next.
Attackers can target a specific entry point like unhandledRejection over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade next to 12.2.4 or later.
If unsure, ask your IT team or search "next CVE-2022-36046" on the vendor's site.
CVE-2022-36046 (next) — CWE-248
Attack vector: remote (network-reachable) / no user interaction
Attack surface: unhandledRejection
Patched: 12.2.4 — 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-248) exists in next. Attackers reach the vulnerable code path via unhandledRejection.
Check the vendor advisory for the affected versions of next. Attack surface: unhandledRejection.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 12.2.4.
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 12.2.4ステージング環境で 12.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com