<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-24T14:29:28.180586+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-114133</id>
    <title>fkie_cve-2026-114133</title>
    <updated>2026-10-24T14:29:28.182866+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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 .</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-114133"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-xfq5-w38q-pc2x</id>
    <title>GHSA-xfq5-w38q-pc2x — Nuxt server islands render `useHeadSafe` input without sanitisation</title>
    <updated>2026-10-24T14:29:28.182943+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nuxt</p>
<p>## Impact</p>
<p>`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 `&lt;script&gt;` tags are only kept for JSON types.</p>
<p>When `useHeadSafe` is called inside a server island (a `.server.vue` component or page, or a component rendered with `&lt;NuxtIsland&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. `&lt;NuxtIsland&gt;` then pushes that input into the page's head as a regular entry, both during server rendering and when hydrating or refetching on the client.</p>
<p>As a result, input that `useHeadSafe` would normally strip (such as `bodyAttrs.onload` or executable `&lt;script&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's origin.</p>
<p>```vue
&lt;!-- components/AuthorMeta.server.vue --&gt;
&lt;script setup lang="ts"&gt;
const { data: author } = await useFetch('/api/author')
// author.value.head is user-authored, e.g. { bodyAttrs: { onload: '...' } }
useHeadSafe(author.value.head)
&lt;/script&gt;
```</p>
<p>## Mitigating factors</p>
<p>- Server components are experimental. They are only active when the application defines a `.server.vue` component or page, or enables `experimental.componentIslands` and renders `&lt;NuxtIsland&gt;`.
- Exploitation requir…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-xfq5-w38q-pc2x"/>
  </entry>
</feed>
