All vulnerabilities

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
Weakness
CWE-524Missing authorization (CWE-862)
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.

From nuxt/nuxt's security advisory. Shortened; the full text is there.

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.
Workarounds as given by nuxt/nuxt's security advisory.

Affected software

SoftwareAffected versions
NuxtServers and applications · github:nuxt/nuxt
  • From 4.4.0 before 4.5.1

About Nuxt

JavaScript framework

From Wikidata, CC0 1.0.
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

ReleaseLatestSecurity fixes
44.6.4Yes
33.21.11Ended 31 Jul 2026
22.18.1Ended 30 Jun 2024
11.4.5Ended 21 Sept 2019

From endoflife.date.

References