Nuxt (4.4.0, 4.5.0) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/nuxt-4.4.0-4.5.0/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 05 Aug 2026 21:25:24 +0000Nuxt 4.x Runtime Payload Cache Disclosurehttps://feed.craftedsignal.io/briefs/2026-08-nuxt-payload-leak/Wed, 05 Aug 2026 21:25:24 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-nuxt-payload-leak/A vulnerability in Nuxt 4.4.0 through 4.5.0 causes sensitive SSR data in the payload cache to be disclosed to unauthorized users due to an insufficient cache key implementation.Nuxt versions 4.4.0 through 4.5.0 contain a vulnerability (CVE-2026-71316) where the runtime payload cache incorrectly stores and retrieves data. The vulnerability resides in the cache:nuxt:payload storage, which utilizes a path-only cache key, ignoring session-specific context such as cookies, authorization headers, or cache variations. This allows an attacker to access sensitive SSR data by requesting the /_payload.json endpoint for routes that have been previously 'warmed' by an authenticated user. The SSR data typically includes results from useFetch or useAsyncData, which may contain private information like profile details, tenant identifiers, or billing data. The issue is specific to the 4.x release line and was caused by a regression where runtime payload-cache reads and writes were no longer restricted to the prerendering phase.

Attack Chain

  1. The target application is configured with routeRules using cache, swr, or isr on protected pages that display user-specific data.
  2. An authenticated user accesses a protected, cached route, triggering the server to generate and store the SSR payload in the cache:nuxt:payload store.
  3. The cached payload is stored using only the URL path as the key, lacking any session or authorization awareness.
  4. An attacker or an unauthorized user identifies a target path that utilizes Nuxt payload extraction.
  5. The attacker issues a GET request to /<target-path>/_payload.json.
  6. The Nuxt renderer retrieves the stored payload from the shared cache before any route middleware, page guards, or authorization checks are executed.
  7. The sensitive payload, intended only for the original authenticated user, is returned to the unauthorized requester in the response body.

Impact

Successful exploitation leads to unauthorized access to sensitive application data rendered during SSR. This exposure impacts users across different sessions, including the disclosure of profile information, billing details, and internal application data to unauthenticated clients. Any application relying on Nuxt 4.4.0-4.5.0 with caching enabled on authenticated routes is at risk.

Recommendation

  • Upgrade to nuxt@4.5.1 immediately to restore proper prerendering gates on payload caching.
  • If upgrading is not immediately feasible, set experimental.payloadExtraction: false in the Nuxt configuration to disable the vulnerable endpoint.
  • Audit routeRules to remove cache, swr, or isr configurations from pages that display user-specific data.
  • Implement authentication requirements at the edge, such as CDN or proxy-level, specifically for /**/_payload.json paths as a temporary defense-in-depth measure.
  • Purge CDN and platform caches after applying security updates to ensure potentially leaked payloads are removed from intermediate storage.
]]>highadvisoryremote-code-executionnuxttemplate-injectioncve-2026-71320