Servers and applications
CVE-2026-71316
Nuxt runtime payload cache discloses another user's SSR data across users and to unauthenticated clients
- Severity
- High 7.5
- Published
- 27 Jul 2026
- Last changed
- 5 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.5.1
- Exploit chance
- 0.5% in the next 30 daysHigher than 44% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Also known as
- GHSA-wm8w-6qjm-cv43
- Sources
- Project advisories (GitHub)
Description
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.
Workarounds
- Set experimental.payloadExtraction: false (reporter-validated): the standalone /_payload.json endpoint returns 404 and the page still serves a 200 with an inline payload.
- Do not apply cache / swr / isr to authenticated pages that render user-specific SSR data.
- As defense-in-depth, require authentication for /**/_payload.json at a proxy / CDN.
- After upgrading, purge any CDN / platform cache that may already hold protected payloads.
Affected software
| Software | Affected versions |
|---|---|
NuxtServers and applications · github:nuxt/nuxt |
|
About Nuxt
JavaScript framework
- Developers who used it in the past year
- 4%Stack Overflow Developer Survey 2025, 2025
- Weekly downloads (npm)
- 3,404,733npm, 15 Nov 2026
- GitHub stars
- 61,078GitHub, 15 Nov 2026
- Forks
- 5,837GitHub, 15 Nov 2026
- Latest release
- v4.6.4GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- JavaScript, Vue.jsWikidata
- First published on GitHub
- 26 Oct 2016GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4 | 4.6.4 | Yes |
| 3 | 3.21.11 | Ended 31 Jul 2026 |
| 2 | 2.18.1 | Ended 30 Jun 2024 |
| 1 | 1.4.5 | Ended 21 Sept 2019 |
From endoflife.date.
Vulnerabilities in Nuxt
- In our list
- 49
- Published in the last 12 months
- 46
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- CVE-2023-54417Nuxt 3.0.0 < 3.4.2 Unauthenticated File Read via vite-node Dev ServerHigh 8.7 18 Nov 2026
- CVE-2023-54418Nuxt 3.0.0-rc.1 < 3.0.0-rc.13 Unauthenticated Arbitrary File Read via Vite Dev ServerHigh 8.7 18 Nov 2026
- GHSA-r99w-jh2x-3mg9Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- CVE-2026-128077Incomplete fix for GHSA-9v7c-q64q-vv33: a leading `//` in the request path bypasses `server/middleware` path checks and server route rules on page routesMedium 6.5 2 Nov 2026
- GHSA-hf59-9xwc-2g4pColliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
- CVE-2026-128076Colliding island props can share one `/__nuxt_island` path (incomplete fix for CVE-2026-46342)Low 3.1 2 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-71316
- GitHub Advisory Database https://github.com/advisories/GHSA-wm8w-6qjm-cv43
- github.com https://github.com/nuxt/nuxt/security/advisories/GHSA-wm8w-6qjm-cv43