<?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://db.gcve.eu</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>Sat, 24 Oct 2026 20:31:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-114133</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-114133</link>
      <description>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. From 3.13.0 until 4.6.2, the server-island renderer serializes raw useHeadSafe entry input into the island response without preserving the safe-input marker, and NuxtIsland later inserts that input into the page head as an ordinary entry. An application that passes attacker-controlled data to useHeadSafe in a .server.vue component or page, or in a component rendered through NuxtIsland, can therefore render values normally removed by the allowlist, including event-handler attributes or executable script content, resulting in stored cross-site scripting in the application origin. This issue is fixed in version 4.6.2 .&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. From 3.13.0 until 4.6.2, the server-island renderer serializes raw useHeadSafe entry input into the island response without preserving the safe-input marker, and NuxtIsland later inserts that input into the page head as an ordinary entry. An application that passes attacker-controlled data to useHeadSafe in a .server.vue component or page, or in a component rendered through NuxtIsland, can therefore render values normally removed by the allowlist, including event-handler attributes or executable script content, resulting in stored cross-site scripting in the application origin. This issue is fixed in version 4.6.2 .&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-114133</guid>
    </item>
    <item>
      <title>GHSA-xfq5-w38q-pc2x — Nuxt server islands render `useHeadSafe` input without sanitisation</title>
      <link>https://db.gcve.eu/vuln/ghsa-xfq5-w38q-pc2x</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;`useHeadSafe` restricts head input to an allowlist of safe tags and attributes. For example, `bodyAttrs` is limited to `class` and `style`, event handler attributes are removed, and `&amp;lt;script&amp;gt;` tags are only kept for JSON types.&lt;/p&gt;
&lt;p&gt;When `useHeadSafe` is called inside a server island (a `.server.vue` component or page, or a component rendered with `&amp;lt;NuxtIsland&amp;gt;`), the island renderer serialises the raw input of every head entry into the island response without the option that marks it as safe input. `&amp;lt;NuxtIsland&amp;gt;` then pushes that input into the page&amp;#39;s head as a regular entry, both during server rendering and when hydrating or refetching on the client.&lt;/p&gt;
&lt;p&gt;As a result, input that `useHeadSafe` would normally strip (such as `bodyAttrs.onload` or executable `&amp;lt;script&amp;gt;` content) is rendered into the page. If an application passes user-controlled data to `useHeadSafe` inside a server island, an attacker who controls that data can achieve stored cross-site scripting on the application&amp;#39;s origin.&lt;/p&gt;
&lt;p&gt;```vue
&amp;lt;!-- components/AuthorMeta.server.vue --&amp;gt;
&amp;lt;script setup lang=&amp;#34;ts&amp;#34;&amp;gt;
const { data: author } = await useFetch(&amp;#39;/api/author&amp;#39;)
// author.value.head is user-authored, e.g. { bodyAttrs: { onload: &amp;#39;...&amp;#39; } }
useHeadSafe(author.value.head)
&amp;lt;/script&amp;gt;
```&lt;/p&gt;
&lt;p&gt;## Mitigating factors&lt;/p&gt;
&lt;p&gt;- Server components are experimental. They are only active when the application defines a `.server.vue` component or page, or enables `experimental.componentIslands` and renders `&amp;lt;NuxtIsland&amp;gt;`.
- Exploitation requir…&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;`useHeadSafe` restricts head input to an allowlist of safe tags and attributes. For example, `bodyAttrs` is limited to `class` and `style`, event handler attributes are removed, and `&amp;lt;script&amp;gt;` tags are only kept for JSON types.&lt;/p&gt;
&lt;p&gt;When `useHeadSafe` is called inside a server island (a `.server.vue` component or page, or a component rendered with `&amp;lt;NuxtIsland&amp;gt;`), the island renderer serialises the raw input of every head entry into the island response without the option that marks it as safe input. `&amp;lt;NuxtIsland&amp;gt;` then pushes that input into the page&amp;#39;s head as a regular entry, both during server rendering and when hydrating or refetching on the client.&lt;/p&gt;
&lt;p&gt;As a result, input that `useHeadSafe` would normally strip (such as `bodyAttrs.onload` or executable `&amp;lt;script&amp;gt;` content) is rendered into the page. If an application passes user-controlled data to `useHeadSafe` inside a server island, an attacker who controls that data can achieve stored cross-site scripting on the application&amp;#39;s origin.&lt;/p&gt;
&lt;p&gt;```vue
&amp;lt;!-- components/AuthorMeta.server.vue --&amp;gt;
&amp;lt;script setup lang=&amp;#34;ts&amp;#34;&amp;gt;
const { data: author } = await useFetch(&amp;#39;/api/author&amp;#39;)
// author.value.head is user-authored, e.g. { bodyAttrs: { onload: &amp;#39;...&amp;#39; } }
useHeadSafe(author.value.head)
&amp;lt;/script&amp;gt;
```&lt;/p&gt;
&lt;p&gt;## Mitigating factors&lt;/p&gt;
&lt;p&gt;- Server components are experimental. They are only active when the application defines a `.server.vue` component or page, or enables `experimental.componentIslands` and renders `&amp;lt;NuxtIsland&amp;gt;`.
- Exploitation requir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xfq5-w38q-pc2x</guid>
    </item>
  </channel>
</rss>
