<?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 21:40:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326849</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326849</link>
      <description>EUVD-2026-326849</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326849</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49993</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49993</link>
      <description>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. In @nuxt/rspack-builder and @nuxt/webpack-builder from versions 3.15.4 to before 3.21.7 and 4.0.0 to before 4.4.7, there is an incomplete fix for GHSA-6m52-m754-pw2g. Source code may still be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. nuxt dev --host) and the developer opens a malicious site on the same network. This issue has been patched in versions 3.21.7 and 4.4.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nuxt is an open-source web development framework for Vue.js. In @nuxt/rspack-builder and @nuxt/webpack-builder from versions 3.15.4 to before 3.21.7 and 4.0.0 to before 4.4.7, there is an incomplete fix for GHSA-6m52-m754-pw2g. Source code may still be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. nuxt dev --host) and the developer opens a malicious site on the same network. 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/fkie_cve-2026-49993</guid>
    </item>
    <item>
      <title>GHSA-x6qj-4h56-5rj5 — @nuxt/webpack-builder and @nuxt/rspack-builder dev server same-origin check bypassed when Sec-Fetch-Site, Origin, and R…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x6qj-4h56-5rj5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/webpack-builder, npm: @nuxt/rspack-builder&lt;/p&gt;
&lt;p&gt;### Summary
This is an incomplete fix for [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g). Source code may still be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. `nuxt dev --host`) and the developer opens a malicious site on the same network.&lt;/p&gt;
&lt;p&gt;### Details
The fix for [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) added an `Origin` / `Referer` fallback to the dev-middleware same-origin check, with a `return true` branch when neither header is present so that non-browser clients (curl, the HMR client, address-bar navigation) keep working.&lt;/p&gt;
&lt;p&gt;That fallback is bypassed when a cross-origin attacker request reaches the dev server with all three signal headers absent:&lt;/p&gt;
&lt;p&gt;- `Sec-Fetch-Site` is [not sent by browsers to non-potentially-trustworthy destinations](https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-site-header) (HTTP on a non-loopback address).
- `Origin` is not sent on non-CORS subresource fetches (a bare `&amp;lt;script&amp;gt;` with no `crossorigin`).
- `Referer` can be suppressed by the attacker page with `&amp;lt;meta name=&amp;#34;referrer&amp;#34; content=&amp;#34;no-referrer&amp;#34;&amp;gt;` or `referrerpolicy=&amp;#34;no-referrer&amp;#34;` on the `&amp;lt;script&amp;gt;` element.&lt;/p&gt;
&lt;p&gt;A classic `&amp;lt;script src=&amp;#34;http://VICTIM_LAN_IP:3000/_nuxt/app.js&amp;#34; referrerpolicy=&amp;#34;no-referrer&amp;#34;&amp;gt;` from a non-trustworthy attacker origin produces exactly that header set, the request is allowed, and the attacker page…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nuxt/webpack-builder, npm: @nuxt/rspack-builder&lt;/p&gt;
&lt;p&gt;### Summary
This is an incomplete fix for [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g). Source code may still be stolen during dev when using the webpack / rspack builder if the dev server is bound to a non-loopback address (e.g. `nuxt dev --host`) and the developer opens a malicious site on the same network.&lt;/p&gt;
&lt;p&gt;### Details
The fix for [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) added an `Origin` / `Referer` fallback to the dev-middleware same-origin check, with a `return true` branch when neither header is present so that non-browser clients (curl, the HMR client, address-bar navigation) keep working.&lt;/p&gt;
&lt;p&gt;That fallback is bypassed when a cross-origin attacker request reaches the dev server with all three signal headers absent:&lt;/p&gt;
&lt;p&gt;- `Sec-Fetch-Site` is [not sent by browsers to non-potentially-trustworthy destinations](https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-site-header) (HTTP on a non-loopback address).
- `Origin` is not sent on non-CORS subresource fetches (a bare `&amp;lt;script&amp;gt;` with no `crossorigin`).
- `Referer` can be suppressed by the attacker page with `&amp;lt;meta name=&amp;#34;referrer&amp;#34; content=&amp;#34;no-referrer&amp;#34;&amp;gt;` or `referrerpolicy=&amp;#34;no-referrer&amp;#34;` on the `&amp;lt;script&amp;gt;` element.&lt;/p&gt;
&lt;p&gt;A classic `&amp;lt;script src=&amp;#34;http://VICTIM_LAN_IP:3000/_nuxt/app.js&amp;#34; referrerpolicy=&amp;#34;no-referrer&amp;#34;&amp;gt;` from a non-trustworthy attacker origin produces exactly that header set, the request is allowed, and the attacker page…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x6qj-4h56-5rj5</guid>
    </item>
  </channel>
</rss>
