<?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>Sun, 25 Oct 2026 09:53:12 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-114130</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-114130</link>
      <description>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.0, an incomplete fix for CVE-2026-53722 allows an application with pages disabled to render a script-capable URL through NuxtLink when attacker-controlled input bound to to is prefixed with an ASCII C0 control character. The no-pages router classifies the value as an internal route before the earlier protocol check and passes it to the rendered anchor href; browsers remove the leading control character and interpret the remaining javascript: URL. The default anchor and NuxtLink custom output are affected, the unsafe href is present in server-rendered HTML, and a victim must click the link for script to execute in the application&amp;#39;s origin. This issue is fixed in version 4.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.0, an incomplete fix for CVE-2026-53722 allows an application with pages disabled to render a script-capable URL through NuxtLink when attacker-controlled input bound to to is prefixed with an ASCII C0 control character. The no-pages router classifies the value as an internal route before the earlier protocol check and passes it to the rendered anchor href; browsers remove the leading control character and interpret the remaining javascript: URL. The default anchor and NuxtLink custom output are affected, the unsafe href is present in server-rendered HTML, and a victim must click the link for script to execute in the application&amp;#39;s origin. This issue is fixed in version 4.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-114130</guid>
    </item>
    <item>
      <title>GHSA-jjm6-p2m9-9w4x — Nuxt: Incomplete fix for GHSA-934w-87qh-qr26: a `javascript:` URL prefixed with an ASCII control character executes fro…</title>
      <link>https://db.gcve.eu/vuln/ghsa-jjm6-p2m9-9w4x</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;An application that renders `&amp;lt;NuxtLink :to=&amp;#34;...&amp;#34;&amp;gt;` with a value it does not control can be made to render an anchor whose `href` executes script in the application&amp;#39;s origin when clicked.&lt;/p&gt;
&lt;p&gt;This is an incomplete fix for [GHSA-934w-87qh-qr26](https://github.com/nuxt/nuxt/security/advisories/GHSA-934w-87qh-qr26) (CVE-2026-53722). It only affects applications running without a `pages/` directory, where `pages` resolves to `false` and Nuxt registers its own router in place of vue-router. Applications using vue-router are not affected.&lt;/p&gt;
&lt;p&gt;Prefixing `javascript:` with an ASCII C0 control character, for example `%01`, meant the value was not recognised as having a protocol. It was classified as an internal route and so never reached the protocol check added in GHSA-934w-87qh-qr26, and the router used for `pages: false` passed it through to the rendered `href` unchanged. Browsers strip the leading control character and run the result as a script URL.&lt;/p&gt;
&lt;p&gt;Both `&amp;lt;NuxtLink custom&amp;gt;` and the default anchor are affected, and the `href` is present in the server-rendered HTML.&lt;/p&gt;
&lt;p&gt;## Mitigating factors&lt;/p&gt;
&lt;p&gt;- The application must have `pages` disabled (no `pages/` directory, or `pages: false`).
- The application must bind untrusted input to `:to`.
- A victim must click the rendered link.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;`nuxt` `&amp;lt;4.6.0`, including all Nuxt 3 releases. Versions before `4.4.7` and `3.21.7` are also affected by GHSA-934w-87qh-qr26.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `nuxt@4.6.0`. Nuxt 3 reached end of l…&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;An application that renders `&amp;lt;NuxtLink :to=&amp;#34;...&amp;#34;&amp;gt;` with a value it does not control can be made to render an anchor whose `href` executes script in the application&amp;#39;s origin when clicked.&lt;/p&gt;
&lt;p&gt;This is an incomplete fix for [GHSA-934w-87qh-qr26](https://github.com/nuxt/nuxt/security/advisories/GHSA-934w-87qh-qr26) (CVE-2026-53722). It only affects applications running without a `pages/` directory, where `pages` resolves to `false` and Nuxt registers its own router in place of vue-router. Applications using vue-router are not affected.&lt;/p&gt;
&lt;p&gt;Prefixing `javascript:` with an ASCII C0 control character, for example `%01`, meant the value was not recognised as having a protocol. It was classified as an internal route and so never reached the protocol check added in GHSA-934w-87qh-qr26, and the router used for `pages: false` passed it through to the rendered `href` unchanged. Browsers strip the leading control character and run the result as a script URL.&lt;/p&gt;
&lt;p&gt;Both `&amp;lt;NuxtLink custom&amp;gt;` and the default anchor are affected, and the `href` is present in the server-rendered HTML.&lt;/p&gt;
&lt;p&gt;## Mitigating factors&lt;/p&gt;
&lt;p&gt;- The application must have `pages` disabled (no `pages/` directory, or `pages: false`).
- The application must bind untrusted input to `:to`.
- A victim must click the rendered link.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;`nuxt` `&amp;lt;4.6.0`, including all Nuxt 3 releases. Versions before `4.4.7` and `3.21.7` are also affected by GHSA-934w-87qh-qr26.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `nuxt@4.6.0`. Nuxt 3 reached end of l…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jjm6-p2m9-9w4x</guid>
    </item>
  </channel>
</rss>
