Vulnerability in next (CVE-2026-94544)
Summary
Vulnerability in next (CVE-2026-94544). Risk of unauthorized operations or information disclosure. Exploitable via experimental.useCache. Mitigation: upgrade to 16.3.8 or later.
Original description
The description as published by the source.
Pending use cache fills are shared across requests for the same key without distinguishing Draft Mode requests from regular requests. When two such requests overlap, the second request receives the first request's fill:
- A regular request that overlaps an editor's Draft Mode request receives unpublished content, without any authentication.
- A Draft Mode request that overlaps a regular request receives published content instead of the draft.
If the overlapping regular request prerenders a page — for example an on-demand prerender of a route that was not prerendered at build time — the unpublished content can be persisted into the generated page and served to all later visitors of that route until the page is revalidated. Since cached functions can be shared across routes, the poisoned page does not need to be the page the editor is previewing.
Sites are affected if they enable Cache Components (or experimental.useCache) and serve Draft Mode previews whose cached functions return draft-dependent content.
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-94544 has been found in next.
Attackers can target a specific entry point like experimental.useCache over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade next to 16.3.8 or later.
If unsure, ask your IT team or search "next CVE-2026-94544" on the vendor's site.
CVE-2026-94544 (next) — CWE-524 / CVSS v3 4.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: experimental.useCache
Patched: 16.3.8 — 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. Attackers reach the vulnerable code path via experimental.useCache without authentication.
Check the vendor advisory for the affected versions of next. Attack surface: experimental.useCache.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to 16.3.8.
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 16.3.8ステージング環境で 16.3.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 nvd.nist.gov
- web github.com