ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-71316

Nuxt runtime payload cache discloses another user's SSR data across users and to unauthenticated clients

Published Jul 27, 2026 · catalog updated Aug 5, 2026 · Nuxt runtime payload cache

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-71316. EPSS is 0.51%. Act only if a listed version of Nuxt runtime payload cache is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Nuxt runtime payload cache).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.51%
Remediation
Version ranges on file
Affected products
npm nuxt

### Impact When a page is covered by / / , Nuxt enables runtime payload extraction and serves . On affected versions the renderer stored the SSR payload in the shared storage under a path-only key (no cookie, , or 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 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 / (for example : 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. does not mitigate it, because the payload cache ignores . Introduced when runtime payload extraction landed for cached routes (#34410); the regression is specific to the 4.x line, where the runtime storage was added and the 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 . Runtime payload-cache reads and writes are again confined to prerendering ( ); at runtime, follows the normal render path so route middleware, , and page guards run for the current request. / v5 and the line already had this property, so 3.x is not affected. ### Workarounds - Set (reporter-validated): the standalone endpoint returns 404 and the page still serves a 200 with an inline payload. - Do not apply / / to authenticated pages that render user-specific SSR data. - As defense-in-depth, require authentication for at a proxy / CDN. - After upgrading, purge any CDN / platform cache that may already hold protected payloads. ### References - Introducing change: #34410 (runtime payload extraction / inline payload for cached routes), commit - Patched-line reference: / v5 and keep the gate

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm nuxt>= 4.4.0, <= 4.5.0

How to fix CVE-2026-71316

  • Upgrade

    CVE-2026-71316 lists a fix boundary at 4.5.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 4.5.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-71316. EPSS is 0.51%. Act only if a listed version of Nuxt runtime payload cache is installed.

Which versions are affected?

Compare what you have installed with >= 4.4.0, <= 4.5.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-524; CWE-862: Missing Authorization. EPSS 0.51%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nuxt security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 27, 2026 · Maintainer security tabs

    Detected

    ### Impact When a page is covered by / / , Nuxt enables runtime payload extraction and serves . On affected versions the renderer stored the SSR payload in the shared storage under a path-only key (no cookie, , or 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

  2. Aug 5, 2026 · Maintainer security tabs

    Updated

    ### Impact When a page is covered by / / , Nuxt enables runtime payload extraction and serves . On affected versions the renderer stored the SSR payload in the shared storage under a path-only key (no cookie, , or 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

Sources

  • Maintainer security tabsVendor advisoryGHSA-wm8w-6qjm-cv43

    ### Impact When a page is covered by / / , Nuxt enables runtime payload extraction and serves . On affected versions the renderer stored the SSR payload in the shared storage under a path-only key (no cookie, , or 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

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026