<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 04:24:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53722 — Nuxt: Reflected XSS in `&lt;NuxtLink&gt;` via unsanitised `javascript:` or `data:` URL</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-53722</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nuxt&lt;/p&gt;
&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. Prior to versions 3.21.7 and 4.4.7, &amp;lt;NuxtLink&amp;gt; did not validate the URL scheme of values bound to its to or href props before rendering them into the href attribute of the underlying &amp;lt;a&amp;gt; element. When an application binds attacker-controlled input (a query parameter, a CMS field, a user-supplied profile URL) to &amp;lt;NuxtLink :to&amp;gt; or :href, the attacker can supply a javascript: or vbscript: URL that is reflected verbatim into the rendered markup. Clicking the link executes the supplied script in the origin of the Nuxt application, resulting in reflected DOM-based cross-site scripting. A data:text/html,... payload reflected through the same sink does not execute in the application&amp;#39;s origin but enables a same-tab phishing surface anchored to a legitimate application link. The same value was exposed to consumers of the component&amp;#39;s custom slot via the href and route.href props, so applications that re-bind those values to their own anchors were affected identically. This issue has been patched in versions 3.21.7 and 4.4.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nuxt&lt;/p&gt;
&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. Prior to versions 3.21.7 and 4.4.7, &amp;lt;NuxtLink&amp;gt; did not validate the URL scheme of values bound to its to or href props before rendering them into the href attribute of the underlying &amp;lt;a&amp;gt; element. When an application binds attacker-controlled input (a query parameter, a CMS field, a user-supplied profile URL) to &amp;lt;NuxtLink :to&amp;gt; or :href, the attacker can supply a javascript: or vbscript: URL that is reflected verbatim into the rendered markup. Clicking the link executes the supplied script in the origin of the Nuxt application, resulting in reflected DOM-based cross-site scripting. A data:text/html,... payload reflected through the same sink does not execute in the application&amp;#39;s origin but enables a same-tab phishing surface anchored to a legitimate application link. The same value was exposed to consumers of the component&amp;#39;s custom slot via the href and route.href props, so applications that re-bind those values to their own anchors were affected identically. This issue has been patched in versions 3.21.7 and 4.4.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-53722</guid>
    </item>
  </channel>
</rss>
