<?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, 17 Nov 2026 06:21:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406474</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406474</link>
      <description>EUVD-2026-406474</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406474</guid>
    </item>
    <item>
      <title>GHSA-x2wv-5868-p7v2 — @nuxt/webpack-builder and @nuxt/rspack-builder dev server serves built source to DNS rebinding pages</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x2wv-5868-p7v2</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&lt;/p&gt;
&lt;p&gt;When using the webpack or rspack builder, the dev server serves built client chunks to any request whose `Host` header matches its `Origin`/`Referer`, or that carries `Sec-Fetch-Site: same-origin`. After a DNS rebinding attack both headers name the attacker&amp;#39;s hostname, so a malicious page opened while `nuxt dev` is running can read `/_nuxt/*.js` and exfiltrate the app&amp;#39;s source. This bypasses the same-origin check added for [GHSA-4gf7-ff8x-hq99](https://github.com/nuxt/nuxt/security/advisories/GHSA-4gf7-ff8x-hq99), [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) and [GHSA-x6qj-4h56-5rj5](https://github.com/nuxt/nuxt/security/advisories/GHSA-x6qj-4h56-5rj5).&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A developer runs `nuxt dev` with `builder: &amp;#39;webpack&amp;#39;` or `builder: &amp;#39;rspack&amp;#39;` (the default config is enough; `--host` is not required) and opens a page on an attacker-controlled hostname, for example `http://rebind.attacker.example:3000/`. The attacker then re-points that hostname at `127.0.0.1`. Requests from the page now reach the dev server as same-origin requests:&lt;/p&gt;
&lt;p&gt;```bash
curl -H &amp;#39;Host: rebind.attacker.example:3000&amp;#39; -H &amp;#39;Sec-Fetch-Site: same-origin&amp;#39; http://127.0.0.1:3000/_nuxt/app.js
# 200, with the compiled modules
```&lt;/p&gt;
&lt;p&gt;The page can read the response with `fetch`, which exposes the compiled source and its inline source maps, module identifiers, the developer&amp;#39;s local filesystem paths, and any developer-controlled values inlined into the client bundle…&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&lt;/p&gt;
&lt;p&gt;When using the webpack or rspack builder, the dev server serves built client chunks to any request whose `Host` header matches its `Origin`/`Referer`, or that carries `Sec-Fetch-Site: same-origin`. After a DNS rebinding attack both headers name the attacker&amp;#39;s hostname, so a malicious page opened while `nuxt dev` is running can read `/_nuxt/*.js` and exfiltrate the app&amp;#39;s source. This bypasses the same-origin check added for [GHSA-4gf7-ff8x-hq99](https://github.com/nuxt/nuxt/security/advisories/GHSA-4gf7-ff8x-hq99), [GHSA-6m52-m754-pw2g](https://github.com/nuxt/nuxt/security/advisories/GHSA-6m52-m754-pw2g) and [GHSA-x6qj-4h56-5rj5](https://github.com/nuxt/nuxt/security/advisories/GHSA-x6qj-4h56-5rj5).&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A developer runs `nuxt dev` with `builder: &amp;#39;webpack&amp;#39;` or `builder: &amp;#39;rspack&amp;#39;` (the default config is enough; `--host` is not required) and opens a page on an attacker-controlled hostname, for example `http://rebind.attacker.example:3000/`. The attacker then re-points that hostname at `127.0.0.1`. Requests from the page now reach the dev server as same-origin requests:&lt;/p&gt;
&lt;p&gt;```bash
curl -H &amp;#39;Host: rebind.attacker.example:3000&amp;#39; -H &amp;#39;Sec-Fetch-Site: same-origin&amp;#39; http://127.0.0.1:3000/_nuxt/app.js
# 200, with the compiled modules
```&lt;/p&gt;
&lt;p&gt;The page can read the response with `fetch`, which exposes the compiled source and its inline source maps, module identifiers, the developer&amp;#39;s local filesystem paths, and any developer-controlled values inlined into the client bundle…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x2wv-5868-p7v2</guid>
    </item>
  </channel>
</rss>
