Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71316 high CVSS 7.5

Vulnerability in nuxt (CVE-2026-71316)

Summary

Vulnerability in nuxt (CVE-2026-71316). Confidential information can be exposed externally. Exploitable via routeRules. Mitigation: upgrade to 4.5.1 or later.

Original description

The description as published by the source.

Impact

When a page is covered by routeRules cache / swr / isr, Nuxt enables runtime payload extraction and serves //_payload.json. On affected versions the renderer stored the SSR payload in the shared cache:nuxt:payload storage under a path-only key (no cookie, authorization, or cache.varies dimension) and, on a later payload request, returned the cached entry before route middleware / page guards ran again.

As a result, once any authenticated user warms a protected, cached page, a subsequent GET //_payload.json from an unauthenticated client or a different authenticated user receives the first user's payload: the full SSR data for that route, including anything loaded via useFetch / useAsyncData (for example /api/me: profile, tenant, billing, token-like values). The HTML response stays correctly varied and protected; only the extracted payload leaks. Both cross-user (A warms, B receives A) and unauthenticated disclosure are exploitable. cache.varies does not mitigate it, because the payload cache ignores varies.

Introduced when runtime payload extraction landed for cached routes (#34410); the regression is specific to the 4.x line, where the runtime cache:nuxt:payload storage was added and the import.meta.prerender gate on the payload-cache read/writes was dropped. The 3.x line shipped the same feature with the gate intact and is not affected.

Patches

Fixed in nuxt@4.5.1. Runtime payload-cache reads and writes are again confine…

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-71316 has been found in nuxt.
Attackers can target a specific entry point like routeRules over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade nuxt to 4.5.1 or later.
If unsure, ask your IT team or search "nuxt CVE-2026-71316" on the vendor's site.

CVE-2026-71316 (nuxt) — CWE-524 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: routeRules / cache / swr / isr
Patched: 4.5.1 — apply immediately
Workaround: set experimental.payloadExtraction: false
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

A vulnerability (CWE-524) exists in nuxt. Attackers reach the vulnerable code path via routeRules without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of nuxt. Attack surface: routeRules / cache / swr / isr.

🔥 Severity

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

🔧 How to fix

Update to 4.5.1.

🛡️ Workaround

Workaround: set experimental.payloadExtraction: false

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nuxt' . 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 'nuxt' . | grep -v node_modules

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

  2. 2
    Apply temporary workaround mitigate 
    set experimental.payloadExtraction: false

    パッチが適用されるまでの応急処置として、set experimental.payloadExtraction: false を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade nuxt to 4.5.1

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

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

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

Affected packages

npm nuxt
[{"type":"SEMVER","events":[{"introduced":"4.4.0"},{"fixed":"4.5.1"}]}]

References

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