<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 20:53:04 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-71316</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-71316</link>
      <description>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. From 4.4.0 until 4.5.1, runtime cache:nuxt:payload entries for /&amp;lt;page&amp;gt;/_payload.json can be returned before route middleware and page guards because import.meta.prerender is not enforced, disclosing another user&amp;#39;s SSR data. This issue is fixed in 4.5.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. From 4.4.0 until 4.5.1, runtime cache:nuxt:payload entries for /&amp;lt;page&amp;gt;/_payload.json can be returned before route middleware and page guards because import.meta.prerender is not enforced, disclosing another user&amp;#39;s SSR data. This issue is fixed in 4.5.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-71316</guid>
    </item>
    <item>
      <title>GHSA-wm8w-6qjm-cv43 — Nuxt runtime payload cache discloses another user's SSR data across users and to unauthenticated clients</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wm8w-6qjm-cv43</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When a page is covered by `routeRules` `cache` / `swr` / `isr`, Nuxt enables runtime payload extraction and serves `/&amp;lt;page&amp;gt;/_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.&lt;/p&gt;
&lt;p&gt;As a result, once any authenticated user warms a protected, cached page, a subsequent `GET /&amp;lt;page&amp;gt;/_payload.json` from an unauthenticated client or a different authenticated user receives the first user&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in `nuxt@4.5.1`. Runtime payload-cache reads and writes are…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;When a page is covered by `routeRules` `cache` / `swr` / `isr`, Nuxt enables runtime payload extraction and serves `/&amp;lt;page&amp;gt;/_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.&lt;/p&gt;
&lt;p&gt;As a result, once any authenticated user warms a protected, cached page, a subsequent `GET /&amp;lt;page&amp;gt;/_payload.json` from an unauthenticated client or a different authenticated user receives the first user&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in `nuxt@4.5.1`. Runtime payload-cache reads and writes are…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wm8w-6qjm-cv43</guid>
    </item>
  </channel>
</rss>
