<?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>Tue, 06 Oct 2026 20:40:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329175</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329175</link>
      <description>EUVD-2026-329175</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329175</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56326</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56326</link>
      <description>&lt;p&gt;Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server-side open redirect vulnerability in navigateTo that fails to properly validate path-normalized payloads like /..//evil.com and /.//evil.com. Attackers can bypass external-host checks using path-normalization techniques to redirect users to attacker-controlled sites via the Location header or meta-refresh, enabling phishing and OAuth authorization-code theft.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt versions 4.0.0 before 4.4.7 and 3.x before 3.21.7 contain a server-side open redirect vulnerability in navigateTo that fails to properly validate path-normalized payloads like /..//evil.com and /.//evil.com. Attackers can bypass external-host checks using path-normalization techniques to redirect users to attacker-controlled sites via the Location header or meta-refresh, enabling phishing and OAuth authorization-code theft.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56326</guid>
    </item>
    <item>
      <title>GHSA-c9cv-mq2m-ppp3 — Nuxt: URL-handling weaknesses in `navigateTo` and `reloadNuxtApp`: SSR open redirect, client-side script execution via…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c9cv-mq2m-ppp3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Three weaknesses in Nuxt&amp;#39;s client-navigation URL handling, all reachable
from documented public APIs (`navigateTo` and `reloadNuxtApp`):&lt;/p&gt;
&lt;p&gt;1. **(CVE-2026-56326) SSR open redirect in `navigateTo` via path-normalisation bypass.** 
   `navigateTo` decided whether a target was external by inspecting the raw
   input with `hasProtocol(..., { acceptRelative: true })`. Inputs such as
   `/..//evil.com`, `/.//evil.com`, `/%2e%2e//evil.com`, or
   `/app/..//evil.com` slipped past that check because they start with
   `/`, but WHATWG URL parsing then normalised them to the
   protocol-relative pathname `//evil.com`. The normalised value was
   written to the `Location` response header and into the
   `&amp;lt;meta http-equiv=&amp;#34;refresh&amp;#34;&amp;gt;` body of the SSR redirect page, so a
   victim&amp;#39;s browser would resolve the redirect cross-origin to the
   attacker&amp;#39;s host.&lt;/p&gt;
&lt;p&gt;2. **(CVE-2026-56698) Client-side script execution via `navigateTo({ open: ... })`.** The
   client-side early-open handler called `window.open(toPath, ...)` without
   applying the `isScriptProtocol` check that gates the normal `navigateTo`
   path. A target of `javascript:...` (or another script-capable scheme)
   passed to `navigateTo(url, { open: { ... } })` therefore executed in the
   application&amp;#39;s origin instead of being rejected.&lt;/p&gt;
&lt;p&gt;3. **(CVE-2026-56697) Open redirect in `reloadNuxtApp` via protocol-relative bypass.**
   `reloadNuxtApp({ path })` rejects script-capable protocols by parsing
   the path with `new URL(path…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Three weaknesses in Nuxt&amp;#39;s client-navigation URL handling, all reachable
from documented public APIs (`navigateTo` and `reloadNuxtApp`):&lt;/p&gt;
&lt;p&gt;1. **(CVE-2026-56326) SSR open redirect in `navigateTo` via path-normalisation bypass.** 
   `navigateTo` decided whether a target was external by inspecting the raw
   input with `hasProtocol(..., { acceptRelative: true })`. Inputs such as
   `/..//evil.com`, `/.//evil.com`, `/%2e%2e//evil.com`, or
   `/app/..//evil.com` slipped past that check because they start with
   `/`, but WHATWG URL parsing then normalised them to the
   protocol-relative pathname `//evil.com`. The normalised value was
   written to the `Location` response header and into the
   `&amp;lt;meta http-equiv=&amp;#34;refresh&amp;#34;&amp;gt;` body of the SSR redirect page, so a
   victim&amp;#39;s browser would resolve the redirect cross-origin to the
   attacker&amp;#39;s host.&lt;/p&gt;
&lt;p&gt;2. **(CVE-2026-56698) Client-side script execution via `navigateTo({ open: ... })`.** The
   client-side early-open handler called `window.open(toPath, ...)` without
   applying the `isScriptProtocol` check that gates the normal `navigateTo`
   path. A target of `javascript:...` (or another script-capable scheme)
   passed to `navigateTo(url, { open: { ... } })` therefore executed in the
   application&amp;#39;s origin instead of being rejected.&lt;/p&gt;
&lt;p&gt;3. **(CVE-2026-56697) Open redirect in `reloadNuxtApp` via protocol-relative bypass.**
   `reloadNuxtApp({ path })` rejects script-capable protocols by parsing
   the path with `new URL(path…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c9cv-mq2m-ppp3</guid>
    </item>
  </channel>
</rss>
