<?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-25T18:26:50.538406+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-114130</id>
    <title>fkie_cve-2026-114130</title>
    <updated>2026-10-25T18:26:50.617492+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. 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's origin. This issue is fixed in version 4.6.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-114130"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-jjm6-p2m9-9w4x</id>
    <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>
    <updated>2026-10-25T18:26:50.617585+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>An application that renders `&lt;NuxtLink :to="..."&gt;` with a value it does not control can be made to render an anchor whose `href` executes script in the application's origin when clicked.</p>
<p>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.</p>
<p>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.</p>
<p>Both `&lt;NuxtLink custom&gt;` and the default anchor are affected, and the `href` is present in the server-rendered HTML.</p>
<p>## Mitigating factors</p>
<p>- 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.</p>
<p>## Affected versions</p>
<p>`nuxt` `&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.</p>
<p>## Patches</p>
<p>Fixed in `nuxt@4.6.0`. Nuxt 3 reached end of l…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-jjm6-p2m9-9w4x"/>
  </entry>
</feed>
